03 - Replication Conflicts

Owned by Paul Steffensen (Unlicensed)
Last updated: Aug 27, 2014 by Arjen Visser
1 min read

When you have more than one copy of data, you run the risk of those copies being different when they shouldn't be. In logical replication speak, that's a conflict (also known as a collision).

Detecting when a conflict occurs and then fixing it so your data is back in sync is a major component of any logical replication product.

There are different types of logical replication conflicts.

  • Delete conflict is where the record to be deleted can't be found in the target database.
  • Insert conflict is where the record to be inserted already exists in the target database.
  • Update conflict is where the old values of the target record don't match the old values of the source record.

Lets explore some of the conflict detection and resolution capabilities of Dbvisit Replicate.

Next steps

Follow the step by step guide in the "Child Pages" below.