How to resolve conflicts in merge replication?

How to resolve conflicts in merge replication?

By default, merge replication uses priority-based logic to resolve conflicts. If a conflicting change is made in two Subscriber databases, the change for the Subscriber with the higher subscription priority wins, or if the priority is the same, the first change to reach the Publisher wins.

How to resolve conflicts in SQL Server?

Resolve conflicts

1. Connect to the Publisher (or Subscriber if appropriate) in Microsoft SQL Server Management Studio, and then expand the server node.
2. Expand the Replication folder, and then expand the Local Publications folder.

How is merge replication used to resolve conflicts?

By default, merge replication uses priority-based logic to resolve conflicts. If a conflicting change is made in two Subscriber databases, the change for the Subscriber with the higher subscription priority wins, or if the priority is the same, the first change to reach the Publisher wins.

Where to find conflict data in replication viewer?

Conflict data is available in the Replication Conflict Viewer for the amount of time specified for the conflict retention period (with a default of 14 days). To set the conflict retention period, either:

Where is conflict information stored in SQL Server?

By default, conflict information is stored: At the Publisher and Subscriber if the publication compatibility level is 90RTM or higher. At the Publisher if the publication compatibility level is lower than 80RTM. At the Publisher if Subscribers are running SQL Server Compact.

How to set conflict logging behavior in merge publication?

The conflict logging behavior of a merge publication is set by using the @conflict_logging parameter of sp_addmergepublication. Use of the @centralized_conflicts parameter has been deprecated. The following table describes the values of these columns based on the value specified for @conflict_logging.