Evgeniy Gribkov posts

In this article, we will examine the process of populating the employee database with dummy data, whose schema we designed in the previous part. Filling a SQL database with dummy data can be very useful when we want to run some tests. The most convenient way is the population of SQL tables with random data with the help of visual data generation tools.

It is a common practice that a DB architect has to design a relational database tailored to a particular solution.

In the course of time, we can experience situations when some certain database objects have not been distributed on one or several databases or database instances. This can happen for a number of reasons. An example of that would be a case when a stored procedure refers to a nonexistent table. In this article, we are going to take a closer look at the issue of how to find invalid objects in SQL Server databases with the help of dbForge SQL Complete.

Quite enough, there’s a need to change how data is displayed in a database so that the users could analyze it more easily. One of the cases of such transformation is transposing data from rows to columns in SQL Server.

Systems often work with distributed databases that contain distributed tables. Distribution is supported by various mechanisms, including replication. In this case, it is necessary to constantly maintain the synchronization of a particular data segment. It is also necessary to check the synchronization itself. This is when the need to compare data in two tables appears.

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. 

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.

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.