Microsoft Replication Conflict Viewer (Queued Updating Subscription)
The Replication Conflict Viewer allows you to view any conflicts that have occurred during replication synchronization. Conflicts occur when the same data is modified at two separate servers, for example, at a Publisher and Subscriber, or at two different Subscribers. The following conflicts can occur:
- Update and insert conflicts. This conflict happens when the same data is changed at two locations. One change wins, and the other one loses.
- Delete conflicts. This conflict occurs when the same row is deleted at one location and changed at the other.
Conflicts are resolved during synchronization according to the conflict revolver you specified when adding articles to the publication. The conflict resolver choices for queued updating subscriptions are:
- Publisher wins and the subscription is reinitialized.
- Publisher wins.
- Subscriber wins.
During conflict resolution the data from the losing row is written to a conflict table. You should periodically review conflicts to help reduce the size of the conflict tracking tables.
Note
The Replication Conflict Viewer displays conflicts that occur in merge replication and in transactional replication when queued updating subscriptions are used. When queued updating subscriptions are used, you can use Replication Conflict Viewer to observe conflicts, but you cannot choose a different resolution for the conflict.
Options
The Replication Conflict Viewer is divided into two sections. The upper section of the dialog box shows the conflict list for the selected table. When you click an item in the conflict list, the details of the conflict are displayed in the lower section of the dialog box.
The conflict data in the lower section is displayed in two corresponding columns (Conflict Winner and Conflict Loser). If the conflict is between updated and deleted data, there may be no data to show for the deleted side of the conflict. In this case, the Replication Conflict Viewer displays a message in one of the columns, indicating the row was deleted at one location and updated at another. It also indicates the suggested resolution.
- Database
Choose a database that includes publications with conflicts.
- Publication
Choose a publication that includes tables with conflicts.
- Table
Choose a table that includes conflicts.
- Define Filter
Click to open the Define Filters dialog box.
- Apply or Remove Filter
Click to apply or remove a filter that has been defined in the Define Filters dialog box.
- Select All
Click to select all conflicts listed in the grid.
- Select None
Click to deselect all conflicts listed in the grid.
- Remove
Click to remove selected conflicts from the viewer and their associated metadata from the replication system tables.
- Show all columns
Select to show all columns of the table.
- Show first five columns and other columns with conflicting data
Select to display the first five columns and any columns that have conflicts. This is helpful when the table has a large number of columns, but you want to see only the columns most relevant to resolving the conflict. The first five columns are always included in this view, as fields that identify a row, such as the primary key or name fields, are often among the first columns of the table.
- Display Column Information (…)
Click to view column information: Table Name, Column Name, Data Type, and Column Value.
- Log the details of the conflict
Check this box to log the details of the conflict to a file. To specify a location for the file, point to the View menu and click Options. Enter a value, or click the browse (...) and navigate to the appropriate file. Click OK to exit the Options dialog box.
See Also
Other Resources
How to: View Data Conflicts for Transactional Publications with Queued Updating Subscriptions (SQL Server Management Studio)
Queued Updating Conflict Detection and Resolution