SQL Server Tools

We are pleased to present the new version of Transaction Log 2.1 – our advanced tool for reading transaction logs and analyzing the history of data changes.

We are delighted to inform our dbForge for SQL Server users that we have just released the hugely updated pack of our SQL Server tools, dbForge SQL Tools, v.6.0. Take a sneak peek of new features and improvements introduced in this release!

In this final part of the three-part article series, we will review creating a script, wrap it in a stored procedure, and will use it for deleting all local temp tables and one particular local temporary table.

In this article, we share a step-by-step guide on how to compare the schema and data of multiple SQL Server databases from the command line.

Having a database under source control brings huge benefits. Therefore, we decided to review and compare two popular version control tools, dbForge Source Control add-in for SSMS and Visual Studio Version Control, to help you pick a tool that meets your needs best.

One of the regular jobs performed by a database administrator and developer is creating and executing queries of higher complexity to resolve complicated tasks. This requires extra caution and seriousness because any inaccuracies in the code can result in undesirable bugs and application downtime.

The article presents a step-by-step guide to SQL INSERT INTO statement. You will learn the basic principles underlying this command and see how to implement this statement visually using dbForge Query Builder.

Very often, developers and QAs need to load a large amount of test data to assess the speed of populating the database with generated data and analyze how the performance changes with the database growth.

If a company has to choose between a free database tool and a paid one, and both of them deliver the same features and performance, it is natural that the paid one doesn’t stand a chance. But what if the free tool doesn’t contain all the necessary functionality for the workflow? What if it has limitations that prevent the employees from becoming more productive? And if it turns out that their work requires either 7 separate, perhaps even hardly compatible free tools, wouldn’t it be more effective to pay for just one tool that would have it all in place?

This is the fifth part of an extensive article dedicated to database versioning. Before you proceed with it, we suggest that you read the previous parts:

• Part I: Version Control with Git
• Part II: Database Versioning with Examples
• Parts III & IV: Database Version Control Using Source Control for SQL Server