The Risk
Why Compare and Synchronize Databases?
Submitted by elvin » Mon 05-Oct-2020, 18:19Subject Area: General | 4 member ratings |
 |
I'll start with the fact that you can compare and synchronize not only data, but also objects on SQL Server, such as procedures, functions, indexes, and so on, i.e. you can compare the entire schema, the structure of the database. In fact, there can be many reasons why it might be necessary to compare two databases in Microsoft SQL Server, here are some possible scenarios:
Let's say you have several databases with a similar structure, changes to which are not clearly controlled, for example, a test bench and an industrial database.
Or you just need to compare and synchronize the data of two databases, in which there is no replication, but the data was entered into one database, and into the other not.
It is also possible that there are several branches, the databases of which are maintained by local developers who can make ad hoc changes (add / delete a column in a table, create an index, etc.), and when it comes to the fact that the databases should to be absolutely identical, serious problems arise.
It is also possible that you have several absolutely identical databases, but at the same time, for some unknown reason, their performance is different, and in order to find out what is the reason, it is just necessary to compare these databases.
4 Comments
