Select objects for synchronization

After you have reviewed the comparison results, you can select the objects you want to synchronize and run the synchronization wizard.

Note

When you select the Source and Target, the sync operation only applies changes to the target database, while the source database remains unchanged.

Select objects for synchronization

By default, all objects are selected for deployment.

Selecting objects to synchronize

Use the checkboxes to undo the selection of objects for synchronization.

You can also use the Operation drop-down menu to select objects:

Operation drop-down menu

  • None is set by default for identical objects and cancels the selection of an object for synchronization. If you change it to Drop, this object will be deleted in Target but will remain intact in Source during the synchronization.

  • Update is set for objects with the Different status and changes the target object according to the source object. You can change it to Drop or None. If you change the action to None, this object will remain intact in Target during the synchronization.

  • Drop is set by default for objects with the Only in Target status. Drop means that the object will be dropped in the target schema. If you change the action to None, this object will remain intact in Target during the synchronization.

  • Create is set by default for objects with the Only in Source status. Create means that the object will be created in the target schema. If you change the action to None, this object will remain intact in Target during the synchronization.

Object status

Schema Compare automatically sets different statuses for compared objects to help you quickly analyze the differences. The statuses are as follows:

  • Only in Source - schema object exists in the source schema and does not exist in the target schema.
  • Only in Target - schema object exists in the target schema and does not exist in the source schema.
  • Different - schema objects with the same names exist in both schemas, but they have different DDL.
  • Equal - identical objects exist in both schemas.
  • Inconsistent - if the Source contains a system-versioned table, and the Target server does not support such objects, this table will be considered inconsistent. System-versioned tables are supported in SQL Server 2016 (13.x) and later.
  • Unknown - object metadata cannot be retrieved, so its status is unknown.

To explore how to remove objects that have the Only in Target status, see Exclude all objects with the Only in Target status.

Synchronize databases

Note

Schema synchronization cannot be rolled back! It may alter or drop schema objects in your Target schema. It is highly recommended to backup the Target database before deploying object changes.

After you have selected objects, you can run the process of synchronization:

1. Click the Synchronize button to open the Schema Synchronization Wizard.

Synchronization wizard

2. Select output options to manage the synchronization script.

You can:

  • Open the synchronization script in the internal editor
  • Save the script to a file
  • Execute the script directly against the target database

3. Click the Synchronize button to close the wizard and complete the synchronization process.

4. Review the sync script, and then execute it by clicking the Execute button on the SQL toolbar.

Execute button

Want to Find out More?

Overview

Overview

Take a quick tour to learn all about the key benefits delivered by dbForge Schema Compare for SQL Server.
All Features

All features

Get acquainted with the rich features and capabilities of the Schema Compare in less than 5 minutes.
Request a demo

Request a demo

If you consider employing the Schema Compare for your business, request a demo to see it in action.
Ready to start using dbForge Schema Compare for SQL Server?