How to: Specify the Conflict Tracking and Resolution Level for Merge Articles (SQL Server Management Studio)

Specify row- or column-level tracking for merge articles on the Properties tab of the Article Properties dialog box, which is available in the New Publication Wizard and the Publication Properties - <Publication> dialog box. For more information about using the wizard and accessing the dialog box, see How to: Create a Publication and Define Articles (SQL Server Management Studio) and How to: View and Modify Publication and Article Properties (SQL Server Management Studio).

With row- and column-level tracking, conflict resolution is always performed at the row-level: the winning row overwrites the losing row. Merge replication also allows you to specify that conflicts be tracked and resolved at the logical record level, but these options are not available from Microsoft SQL Server Management Studio. For information about setting these options from replication stored procedures, see How to: Define a Logical Record Relationship Between Merge Table Articles (Replication Transact-SQL Programming).


If you modify the tracking level after subscriptions have been initialized, those subscriptions must be reinitialized. For more information about the effects of property changes, see Changing Publication and Article Properties.

To specify row- or column-level tracking

  1. On the Articles page of the New Publication Wizard or the Publication Properties - <Publication> dialog box, select a table.

  2. Click Article Properties, and then click Set Properties of Highlighted Table Article or Set Properties of All Table Articles.

  3. On the Properties tab of the Article Properties <Article> dialog box, select one of the following values for the Tracking level property: Row-level tracking or Column-level tracking.

  4. If you are in the Publication Properties - <Publication> dialog box, click OK to save and close the dialog box.

See Also


How Merge Replication Detects and Resolves Conflicts
Detecting and Resolving Conflicts in Logical Records

Help and Information

Getting SQL Server 2005 Assistance