Activity overview
Latest activity by ShadowDBA
Brian Donahue wrote:
Hello,
I think that v71. of the Data Compare Engine had a bug that prevented it from dropping all foreign keys if the foreign keys were placed on a table that was not being compared. At any rate, the behavior doesn't seem right and I would suggest upgrading to the latest SDK: http://www.red-gate.com/MessageBoard/vi ... php?t=9911
So by installing the SQL Comparison SDK 8 Latest Cumulative Patch, I can re-run my SQL Data Compare 7.1 job and it will now actually disable all foreign keys and constraints?
Or does that patch only address issues when using the API and not the SQL Data Comparisno product?
My data comparison job runs for 8 hours and then gives me messages like :
[2627] Violation of PRIMARY KEY constraint 'dbo.event_watch_column_mapping.PK_event_watch_column_mapping.pkey.sql'. Cannot insert duplicate key in object 'dbo.event_watch_column_mapping'.
Also the keys are the same in the source and destination databases, so how are we getting data that would cause this error. And wouldn't this error be generated on re-creating the primary since it is selected to be dropped durring the sync?
In synch behavior I have the following options checked:
Disable Foreign Keys
Drop primary keys, indexes, and nique constraints
use transactions in sql scripts
disable dml triggers
disable ddl triggers
Reseed identity columns
Any help you could provide would be great. / comments
Brian Donahue wrote:
Hello,
I think that v71. of the Data Compare Engine had a bug that prevented it from dropping all foreign keys if the foreign keys were placed on a table that was not being ...