Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

SubscriptionSyncType Enumeration

 

Applies To: SQL Server 2016 Preview

Enumerates options for how the initial synchronization is performed for a subscription.

Namespace:   Microsoft.SqlServer.Replication
Assembly:  Microsoft.SqlServer.Rmo (in Microsoft.SqlServer.Rmo.dll)

public enum SubscriptionSyncType

Member nameDescription
Automatic

Schema and initial data for published tables are transferred to the Subscriber when the initial snapshot is applied.

InitializeFromLSN

Used when you are adding a node to a peer-to-peer transactional replication topology. Used with SubscriptionLSN to make sure that all relevant transactions are replicated to the new node. Assumes that the Subscriber already has the schema and initial data for published tables.

InitializeWithBackup

Schema and initial data for published tables are obtained from a backup of the publication database. This option assumes that the Subscriber has access to a backup of the publication database. This option is only supported for transactional publications. The location of the backup and media type for the backup are specified by BackupDeviceName and BackupDeviceType. When using this option, a peer-to-peer transactional replication topology need not be quiesced during configuration. This option is not supported for subscriptions to non-SQL Server publications. This option is only available for SQL Server 2005 and later.

None

Subscriber already has the schema and initial data for published tables. This option is supported for merge publications. This option has been deprecated for transactional publications. Use ReplicationSupportOnly instead.

ReplicationSupportOnly

Provides automatic generation at the Subscriber of article custom stored procedures and triggers that support updating subscriptions, if appropriate. This option is supported only for transactional publications. This option assumes that Subscriber already has the schema and initial data for published tables. When configuring a peer-to-peer transactional replication topology, ensure that the data at all nodes in the topology is identical. Quiesce the replication topology before configuring peer-to-peer transactional replication using this option. This option is only available for SQL Server 2005 and later.

System tables and data are always transferred.

This namespace, class, or member is supported only in version 2.0 of the .NET Framework.

Return to top

Community Additions

Show:
© 2015 Microsoft