Row Based 2-Way Synchronization

[Kribor]

Hi,

First I thought this might be the answer to our DB merging issues but now I am not so sure. It seems there is “2-way” feature in the DB sync tool but it the information there indicates that it is only able to merge tables if primary keys are not conflicting, or it will override with changes from the “source”-db.

So my real question is, is it possible to make merge a table and have the tool require user input when there are conflicts? I.e. open a diff window of some sort allowing one to shuffle data from one side to the other and then save. Sort of a diff/merge tool.

Cheers,

Kris

[peterlaursen]

Your understanding that 'source will overwrite target' for rows with a PK-conflict is correct . There also is no option for such user interaction as requested.

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.

[Kribor]

'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…

[Author]

Posts