SQL Data Compare - 10.0
Data that was not synchronized - SQL Data Compare
When you synchronize the data sources, some rows may not be synchronized if:
- there are triggers defined on the tables
If you have a trigger defined on a table that inserts data into another table on INSERT, DELETE, or UPDATE, the data in the tables will change as the synchronization is run, which will cause unpredictable results. To avoid this, select the Disable DML triggers project option before you generate the synchronization script.
- primary keys are defined on columns with differing collations
If you compare tables that have primary keys defined on columns that have different collations, SQL Data Compare may produce unpredictable results.
- columns contain timestamp data
SQL Data Compare cannot synchronize data in timestamp columns.
- table structures are not identical
If the structure of the tables that you are synchronizing is not identical, SQL Data Compare may produce unpredictable results.
CLR data that was not synchronized
Data for CLR types can be stored as string or binary values. When CLR data is compared, SQL Data Compare always compares the binary representations. However, by default, when CLR data is synchronized, SQL Data Compare synchronizes the string representations, because binary formats are not always compatible.
If the binary representations are not compatible, they are always displayed as different even if the string representations are identical. String representations do not always contain the full information about the data, so when the databases are re-compared using the binary representations following synchronization, they may be displayed as different.
If you know that the binary formats are compatible, you can select the project configuration option Transport CLR data types as binary.
This forces SQL Data Compare to synchronize the binary representations.
Primary keys, indexes, or unique constraints that were not dropped for synchronization
If you select the project configuration option Drop primary keys, indexes, and unique constraints, note that primary keys, indexes or unique constraints that are selected as comparison keys are not dropped for the synchronization.
See also |
Was this article helpful?
Using SQL Data CompareSQL Data Compare
- Logging and log files
- Internal Connection Fatal Error in versions 4 and 5
- NULL textptr passed to UPDATETEXT function when running synchronization
- How much free hard disk space is required?
- Comparing the data of two tables in the same database
- Suggestions to combat comparison and synchronization performance issues
- SQL comparison and synchronization automation capabilities
- SqlNullValueException occurring in synchronization wizard
- SQL Data Compare command-line XML argument file examples
- Using Windows authentication logons between domains
- Using a filter on a column on related (joined) tables
- Determining minimum database permissions for SQL Data Compare
- Tables with compound keys may not be mapped automatically
- Best practices for synchronizing data
- Cleaning up a SQL script after SQL Compare or SQL Data Compare
- Troubleshooting System.OutOfMemoryException during comparison
- Exception thrown by db reader 1
- Reseed applying "incorrect" identity values
- Running migration scripts using SqlCmd.exe
- This SQL Server has been optimized for x concurrent queries.
- SQL Data Compare showing differences in 2 identical databases
- How to force SQL Compare and SQL Data Compare to use an Encrypted Connection
- Improving the performance of SQL Data Compare
- Logging and log files
- Case-sensitive comparisons
- Tables or views that could not be compared
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Data Compare
- Activating your products
- Activating your products
- Getting help offline
- Getting better performance out of SQL Data Compare
- Release notes - version 10.xx
- SQL Data Compare release notes - version 7.xx
- SQL Data Compare release notes - version 8xx
- SQL Data Compare release notes - version 9.xx
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs
