dbForge Studio for SQL Server enables you to synchronize data after you compare source and target databases.
You can choose which tables and individual records to synchronize. In the data comparison document grid, use the check boxes in the first column to include or exclude objects from synchronization.
dbForge Studio can back up the target database as part of the synchronization process to help prevent accidental data loss.
The synchronization script is divided into batches by GO commands.
GO statements are inserted after DML statements and statements that set server options.
For each table or view, GO is added after the last DML statement.
If a table or view has more than 1000 DML statements or more than 1 MB of statements, the script is split into several batches. In this case, GO is inserted after each 1000 statements or after each 1 MB of script text, whichever occurs first.
You can choose to run synchronization as a single transaction.
Single transaction: If an error occurs, all synchronization actions are rolled back.
Multiple batches: If you do not use a single transaction, all statements before the GO block that contains an error are executed. The statements in that block and in all subsequent blocks are not executed.
If you synchronize data that uses different data types, the wizard can detect potential issues.
Synchronization warnings appear on the Summary page of the Data Synchronization wizard. These warnings indicate that errors or data loss may occur due to rounding, truncation, or other type conversions.
The Data Synchronization wizard lets you:
Before you start synchronization, you can review the Action Plan on the Summary page. It lists all actions that will be performed during synchronization and reflects the structure of the synchronization script.