Primary key has moved on

joshdanhall

Hi,

I'm using Data Compare to create scripts to populate reference data into multiple environments. With the scripts generated I now run into problems because the primary key from one INSERT may no longer be appropriate for the target environment. For example that environment may already have generated a row with that id value, so my script will fail.

Does the Data Compare tool offer a solution for this, or will I have to hand-edit the scripts to handle the dynamic nature of my requirements?

Note: The primary key value is also used in subsequent INSERTs, as it is a foreign key for other table.

Thanks in advance.

Regards, Josh

Andy C S

I'm afraid SQL Data Compare doesn't have multiple-environment support, so there's not really any built-in functionality designed to handle situations like this. Do let us know if you come up with a nice solution, but there's not much I can really offer you, sorry!