What data will not be synchronized?

When you synchronize the two data sources, consider the following cases.

Row synchronization

Row synchronization may fail under the following conditions:

• Triggers defined on the tables.
• Primary keys with different collations.
• Columns with rowversion (formerly timestamp) data.
• Source and target tables with nonidentical structures.

Note

To resolve the issue with the triggers, select Disable DML triggers in the Data Synchronization Wizard before generating the synchronization script.

CLR data that will not be synchronized

CLR data types can be stored as string or binary values. By default, dbForge Studio compares and synchronizes CLR types as strings.

• For large CLR data, select Compare CLR types as binary in the New Data Comparison wizard to improve accuracy.
• Clear Compare CLR types as binary for CLR types that do not implement the Comparable interface.

Primary keys, indexes, and unique constraints

When you select Disable primary keys, indexes and unique constraints in the Data Synchronization Wizard, primary keys, indexes or unique constraints used as comparison keys are preserved during synchronization.