Execute Synchronization

Once you review all the settings and are ready to perform the synchronization, click on the 'Synchronize' button for Executing the Synchronization. DBChangeManager executes the following steps as part of Synchronization:

If the target is a Database:

Connects to the destination database to be synchronized
Executes the synchronization script to synchronize the destination database
On success, displays a brief confirmation message
On failure, rollbacks all the changes done till the instance of failure. Brings back the destination database to the original state as before the start of synchronization. Appropriate error message would be displayed

If the target is a Single SQL Script file:

The file contents will be overwritten with the definitions of the objects that were chosen for synchronization. Definitions of Objects that were not selected for synchronization will be retained as is.

If the target is a Database folder:

Files corresponding to objects that are to be dropped as part of synchronization will be deleted.
Files corresponding to objects that are to be created new as part of synchronization will be created.
Files corresponding to objects that are to be modified as part of synchronization will be modified.

Note: Currently DBChangeManager does not support synchronizing SQL Scripts packaged as a Zip file

Synchronization in Progress

On performing the synchronization DBChangeManager connects to the appropriate destination database and starts executing the synchronization script. When DBChangeManager does the synchronization it presents a progress screen to indicate the progress of Synchronization.

Successful Synchronization

If the synchronization performed by DBChangeManager is successfully done, a message dialog with a "Successfully Synchronized" message will be displayed.

Synchronization Failure

During Synchronization if any failures occurs, DBChangeManager handles it as follows:

Further Synchronization action will be aborted
It will automatically rollback all the changes done till then in the database and will bring it back to the original state as before the start of synchronization
Notify the user about the failure through a message dialog

Note: DBChangeManager currently has a limitation in automatic rollbacks if failures occur on synchronizing user logins, full-text catalogs, schema, role and filegroups objects. You have to take care of rolling back these changes manually. Automatic rollbacks for all other SQL Server objects on failures are supported by DBChangeManager.

Re-comparison

On completion of synchronization, you can choose to compare the resources again using the option provided in the Synchronization progress dialog on completion of the synchronization process.