SQL Server Tools

We are excited to announce that a new version of the SSMS add-in for SQL Server database change management, dbForge Source Control for SQL Server, v2.1, has been just rolled out!

In previous articles, we have reviewed a general algorithm of finding and deleting incomplete open transactions in SQL Server databases, created a table for fixing incomplete transactions and a CRUD-stored procedure, and implemented numerous settings that will make our document workflow productive and handy.

In two previous articles, we have reviewed a solution for deleting incomplete open transactions in SQL Server. 

Just like any information system, databases are constantly changing. Quite often you need to roll back some operations. There is undoubtedly an opportunity to restore the database to a specific point in time and you can also undo the latest transactions with both regular and third-party utilities.

In the first part of the series of our articles on this subject, we presented the general algorithm for deleting open transactions that are not completed from a SQL Server database and considered the process of creating a table to record incomplete transactions. Now, let’s look at the process of creating a CRUD stored procedure to find and delete active transactions in SQL Server.

We are glad to inform our SQL Server users that we have just extended the compatibility of dbForge DevOps Automation for SQL Server with just-released dbForge DevOps Automation Bamboo Plugin for SQL Server.

Devart offers the following tools that are involved in Continuous Integration both directly and indirectly.

Quite often there’s a need to create a read-only replica of a SQL Server database. This might be required, for example, for the purpose of separating analytical and operative tasks. The first cause high load on databases and in order to reduce it, the replica of the primary database is created to perform analytical read-only queries. 

Frequently enough, MS SQL Server open transactions are incompleted and their initiators forget about them. This is quite a commonly encountered situation in routine database development. The most striking example is when one uses SQL Server Management Studio to run a script that starts an explicit transaction with the BEGIN TRANSACTION statement, but then the batch is canceled in the middle of a transaction without issuing a COMMIT or ROLLBACK statement to complete the transaction and the transaction is left open.

The dbForge team is thrilled to present the latest version of SQL Complete for SQL Server. The most notable feature of this release addresses the newly introduced debugging functionality designed to take away the pain of combing through scripts to find errors and grant the possibility to debug T-SQL directly in the IDE. From now on, you don’t need to compromise on code quality.