After you have selected the objects for synchronization, you can use the Schema Synchronization Wizard to set synchronization options.
1. To open the synchronization wizard, click .
2. Click Options tab to view all the synchronization options. Each option has a detailed description.
For convenience, options are grouped:
To locate a required option, you can also type the search text in the Search box.
If you want to use the options you have set later, click Save As My Defaults.
If you want to apply options you have saved earlier, click My Defaults.
It is also possible to return to the default settings of the tool. Click Devart Defaults if you want to do it.
3. After you’ve configured the synchronization options, click Synchronize.
|Default State||Option Group||Option Name||Option Description|
|Enabled||Database backup||Backup path:
||Creates a backup and allows specifying the location of the target database backup file. The backup file name will be generated in the following format: <database_name>_yyyy_MM_dd_hh_mm.bak|
|Disabled||Database backup||Backup type: DIFFERENTIAL||Creates a backup in the selected mode. Please, note that creating a differential database backup requires a previous full database backup. If your database has never been backed up, a full database backup will be created. Copy-only mode option is available for SQL Server 2008 or later versions.|
|Enabled||Database backup||Create folder for database backup||Creates a folder for a database backup.|
|Disabled||Database backup||Extension for backup file||Specifies the extension for a backup file. When the option is disabled, the default extension (.bak) will be used for a backup file.|
|Enabled||Database backup||Use compression for backup||Performs the backup compression. This option is available for SQL Server 2008 or later versions.|
|Enabled||Transactions||Use a single transaction||Executes a synchronization script as a single transaction. All the changes to the databases will be rolled back in case of any error when executing the synchronization script. The option should be disabled when working with the memory-optimized tables, since the execution of the ALTER, DROP, and CREATE DDL is not supported within user transaction|
|Disabled||Transactions||Add error handling statements||Stops executing a script when encountering an error.|
|Enabled||Transactions||Set transaction isolation level to||Sets the transaction isolation level. This option is enabled when the Use a single transaction option is selected. You can specify the following transaction isolation levels: SERIALIZABLE, SNAPSHOT, REPEATABLE READ, READ UNCOMMITTED, READ COMMITTED.|
|Disabled||Common||Add constraints and keys to tables using WITH NOCHECK||Adds the WITH NOCHECK clause to foreign keys and constraints created during synchronization.|
|Disabled||Common||Add WITH ENCRYPTION||Adds WITH ENCRYPTION when stored procedures, functions, views, and triggers are included to the synchronization script.|
|Disabled||Common||Check for object existence||Adds an additional check into the synchronization script (before each object DDL) to verify object existence in the target database.|
|Disabled||Common||Disable DDL triggers||Disables DDL triggers before the synchronization. After the synchronization, the triggers will be enabled.|
|Enabled||Common||Generate fully qualified object names||Generates fully qualified object names in the synchronization script. If the option is enabled, the names of objects in the synchronization script will include a schema name.|
||Adds the USE
|Disabled||Common||Specify the folder for assemblies||Performs assembly synchronization by copying the files to the specified folder. The option allows specifying a local path or network location tp copy the target assemblies to.|
|Disabled||Common||Synchronize a database in the single user mode||Synchronizes a database in the single user mode.|
|Enabled||Common||Update views||Updates the metadata for the specified views that are not schema bound.|
|Disabled||Common||Use ALTER SCHEMA TRANSFER statement||Transfers tables between schemas using the ALTER SCHEMA TRANSFER statement. This option can be enabled if the same database is compared.|
|Disabled||Common||Use DROP and CREATE instead of ALTER for assembles||Replaces ALTER statements with DROP and CREATE statements for assemblies in the synchronization script.|
|Disabled||Common||Use DROP and CREATE instead of ALTER for tables||Replaces ALTER statements with DROP and CREATE statements for tables in the synchronization script. Data will be transferred to the newly created tables.|
|Disabled||Common||Use DROP and CREATE instead of ALTER for views, procedures, functions, and triggers||Replaces ALTER statements with DROP and CREATE statements for views, procedures, functions, and triggers in the synchronization script.|
|Disabled||Common||Verify table data using checksum||Checks if any table data is lost after synchronization. If data is lost, the warning will appear in the Error list after synchronization.|
|Disabled||Script Comments||Comment DDL statements for signatures, symmetric and asymmetric keys as well as certificates||Adds comments to the DDL statements for signatures, symmetric and asymmetric keys as well as certificates.|
|Disabled||Script Comments||Exclude comments||Prevents comments generation in the synchronization script.|
|Disabled||Script Comments||Include print comments||Adds comments to the output when executing the synchronization script. If the print comments are included in the synchronization script, it is easier to locate the items in the output.|