Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

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.

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.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.