Replication Conflict Viewer

When the Merge Agent synchronizes the data changes at a Publisher and Subscriber, it may encounter one of three types of conflicts for each merge:

• Update and insert conflicts, where the same data is changed at two locations.
• Delete conflicts, where the same row is deleted at one location and changed at the other.
• Constraint conflicts, where data changes made at one location violate constraints at another location (known as a divergent conflict). After a divergent conflict has occurred, the data at the two locations are no longer identical until the conflict is resolved.

If the Merge Agent encounters one of these conflicts during the merge process, it calls the conflict resolver specified for the article The conflict resolver determines the winner and loser of the conflict and records the outcome in the conflict_usertablename. The conflicts are resolved based upon the priority set when the subscription was created, or the user-created resolution procedures.

After the merge process is complete, you can use the Replication Conflict Viewer to review the manner in which the conflicts were resolved and make changes to these resolutions. Be sure to connect to the correct server to view the conflicts. The location of the conflict table varies depending upon whether replication has been configured for centralized of decentralize logging of conflicts. If centralized, the conflict table is stored at the Publisher and you must connect to the Publisher to view the conflicts. If decentralized, the conflict table is stored at either the publisher or Subscriber, depending upon who lost the conflicts.

Note The Replication Conflict Viewer displays dates in ISO datetime format instead of the local format.

To view and further resolve synchronization conflicts

To modify where conflicting data changes are reported