Contents
When to use parameterized row filters in merge publications?
When parameterized row filters are used in merge publications, replication initializes each subscription with a two-part snapshot. First, a schema snapshot is created that contains all objects required by replication and the schema of the published objects, but not the data.
How to create parameterized filters ( merge ) in SQL?
For more information about filtering options, see Parameterized Row Filters. Manually generate a snapshot for each Subscriber with the Snapshot Agent. The Subscriber must then provide the snapshot location to the Merge Agent, so it can retrieve and apply the correct snapshot.
How to create a snapshot with parameterized filters?
This topic describes how to create a snapshot for a merge publication with parameterized filters in SQL Server by using SQL Server Management Studio, Transact-SQL, or Replication Management Objects (RMO). When parameterized row filters are used in merge publications, replication initializes each subscription with a two-part snapshot.
When does metadata expire in a merge snapshot?
If the filtering for one or more articles in the publication yields non-overlapping partitions that are unique for each subscription, metadata is cleaned up whenever the Merge Agent runs. This means that the partitioned snapshot expires more quickly.
How to create a snapshot for a publication with parameterized filters?
To create a snapshot for a publication with parameterized filters, see Create a Snapshot for a Merge Publication with Parameterized Filters. The Snapshot Agent creates snapshots for each partition.
Why is the alternate snapshot location a publication property?
Because the alternate snapshot location is a publication property, the Distribution Agent and the Merge Agent are able to locate the proper snapshot as part of the synchronization process.