Comments
1 comment
-
Hi, sorry for the delayed response.
What is your desired behavior here? Depending on that you have a couple of options.
If the primary key could be the same for two records that you want to keep, you should set a different comparison key. By default we choose the Primary Key for this, but you can change it, details on how to do so here:
http://documentation.red-gate.com/displ ... to+compare
If, however, the same primary key implies that you only want to overwrite the data in the target machine, simply keeping this row selected in the comparison results when you start the deployment wizard will result in a script which will alter that row.
In either case foreign keys will be respected.
Hopefully that helps, do say if we've misunderstood.
Michael
Add comment
Please sign in to leave a comment.
Let's say I have a USERS record In DB1 with primary key 1 and a USERS record with the same primary key value in DB2. What is going to happen to the primary keys and their corresponding foreign keys after the merge?