What data will not be synchronized?

Last modified: August 8, 2024

When you synchronize the data sources, bear in mind that some rows may not be synchronized if:

• There are triggers defined on the tables

To circumvent a problem, select the Disable DML triggers option in the Data Synchronization Wizard before generating the synchronization script.

• Primary keys are defined on columns that have different collations

If you try to compare tables that have primary keys defined on columns with differing collations, the results might be unpredictable.

• Columns have timestamp data

The Data Compare for SQL Server tool won’t synchronize data in timestamp columns.

• Tables having nonidentical structures

In case the structure of the tables you are synchronizing is not identical, the outcome might be unpredictable.

CLR data that will not be synchronized

CLR data types can be stored as string or binary values. By default, Data Compare for SQL Server compares and synchronizes CLR types as string. However, it is recommended to enable the Compare CLR types as binary option in the New Dara Comparison Wizard when comparing large CLR data. Nevertheless, do not set this option for the types that do not inherit OComparable interface.

Primary keys, indexes, and unique constraints that will not be dropped for synchronization

When you select the Disable primary keys, indexes and unique constraints option in the Data Synchronization Wizard, bear in mind that primary keys, indexes or unique constraints that are selected as comparison keys will not be dropped for the synchronization.