Article Options for Merge Replication
There are a number of options for merge table articles that allow you to tailor replication behavior to the needs of your applications. With merge replication, you can do the following:
- Specify whether changes at the Subscriber are uploaded to the Publisher. For applications in which some or all data should be read-only at the Subscriber, download-only articles provide a performance benefit. For more information, see Optimizing Merge Replication Performance with Download-Only Articles.
- Specify that deletes for one or more articles should not be tracked by replication triggers and system tables. This option can be useful in a number of application scenarios, including those that use batch deletes that do not need to be replicated. For more information, see Optimizing Merge Replication Performance with Conditional Delete Tracking.
- Specify the processing order of articles to ensure that articles are processed in the order required by your application. For more information, see Specifying the Processing Order of Merge Articles.
- Specify that a set of related records should be processed as a unit (by default, merge replication processes changes to tables on a row-by-row basis). For more information, see Grouping Changes to Related Rows with Logical Records.
- Use conflict detection and resolution for cases in which the same data could be changed at more than one node in a topology. For more information, see Detecting and Resolving Merge Replication Conflicts.
- Specify schema options, such as whether constraints and triggers are copied to the Subscriber. For more information, see How to: Specify Schema Options (SQL Server Management Studio) and How to: Specify Schema Options (Replication Transact-SQL Programming).
- Use row filters, join filters, and column filters. Filtering table articles enables you to create partitions of data to be published. For more information, see Filtering Published Data.