'peterlaursen' wrote:
The advice I use to give in this situation is to avoid PK conflicts in such cases by adding one more (new) column to the PK on every table. This column should be constant on same server but different on different servers.
That's not possible for us since we are using this as a part of our release process. We edit existing entries (already has a primary key) on our Release Candidate, test it and then deploy the DB to prod DB. Whereas the Prod Db some rows might have been “quick-fixed” in the meantime so we can't overwrite everything.
So it seems we are out of luck…