Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 15 Next »

Conflicts and conflict resolution is important in database replication. When a conflict occurs it means there is a potential for the data between the source and target databases to be out of sync. This is also referred to as data divergence.

Dbvisit Replicate has build in conflict detection and conflict resolution features that assist with ensuring data divergence does not occur.

Dbvisit Replicate offers:

  1. Conflict detection to ensure that when there is a possibility of data divergence, a notification or alert is triggered.
  2. Conflict resolution to ensure that when a conflict occurs, enough information about the conflict is shown so that the conflict can be resolved.
  3. Conflict handling to be able to set predefined rules to say what to do when a conflict occurs.
  4. Listing of conflicts to see the SQL that is causing the conflict.

All of the conflict detection, handling, resolution and listing is done from one central place - The Dbvisit Replicate console (dbvrep).

This section discusses all the options and commands around conflict detection and conflict resolution.

 

  • No labels