Enumerates supported publication properties.
Assembly: Microsoft.SqlServer.Rmo (in Microsoft.SqlServer.Rmo.dll)
Anonymous subscriptions can subscribe to the publication. Anonymous subscriptions are required if you want to create a subscription without registering the subscription at the Publisher. This is necessary for cases in which you cannot establish a SQL Server connection to the Publisher during subscription configuration.
This feature will be removed in a future version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible.
Subscribers can initialize a subscription to the publication from a backup rather than the initial snapshot. Supported only for transactional or snapshot replication.
Deletes are sent to the Subscriber when modification of the row on the Publisher causes it to change its partition and when the publication uses parameterized filters. Supported only for merge publications.
Subscriptions where the synchronization agent runs at the Subscriber (pull subscriptions) are supported. Required to support SQL Server Compact Subscribers.
Subscriptions where the synchronization agent runs at the Distributor (push subscriptions) are supported.
Queued updating subscriptions are supported for transactional publications. Supported only for transactional publications.
Subscribers can initiate the snapshot process to generate the filtered snapshot for their data partition when the merge publication has parameterized filters. Supported only for merge publications.
Databases that subscribe to the publication can be copied and attached to create new subscriptions. Attachable subscriptions have been deprecated.
Immediate updating subscriptions are supported for transactional publications. Supported only for transactional publications.
Subscribers can synchronize subscriptions to the merge publication with servers other than the Publisher where the subscription originated. Supported only for merge publications. This feature is deprecated and will be removed in a future release. Not supported for SQL Server Compact Subscribers.
Subscribers can synchronize subscriptions over the Internet using the HTTPS protocol. Supported only for merge publications. Only available with SQL Server 2005. Required to support SQL Server Compact Subscribers. For more information, see Web Synchronization for Merge Replication.
The stored procedure used by updating subscriptions to synchronize with the transactional publication is automatically generated. Supported only for transactional publications.
Conflict records are stored at the Publisher. Supported only for merge publications.
Snapshot files are compressed into the CAB format. Snapshot files that are larger than 2 gigabytes (GB) cannot be compressed. Not supported for SQL Server Compact Subscribers.
Conflict records are stored at the Subscriber. Supported only for merge publications. Not supported for SQL Server Compact Subscribers.
Parameterized row filters are supported on a merge publication. Supported only for a merge publication.
The attribute is EnabledForActiveDirectory.
Non- SQL Server Subscribers are supported. Supported only for transactional and snapshot publications. Only available with SQL Server 2005 and later versions.
Peer-to-peer transactional replication is supported. Supported only for transactional publications. Only available with SQL Server 2005 and later versions.
Synchronization files for the publication are recreated each time the Snapshot Agent runs. Subscribers are able to get the synchronization files immediately if the Snapshot Agent has completed before the subscription is created. New subscriptions get the newest synchronization files generated by the most recent execution of the Snapshot Agent. When setting, must also be set.
Each subscription uses its own replication agent instance when synchronizing with the Publisher. Setting this option reduces latency and is the default for a transactional publication. Merge replication always uses independent agents.
Publication can be synchronized over the Internet, and file transfer protocol (FTP) can be used to transfer the snapshot files to a Subscriber. For more information, see Replication over the Internet.
Partition change optimizations are used when precomputed partitions cannot be used. Do not specify PartitionGroupsOption is True. For more information, see Optimize Parameterized Filter Performance with Precomputed Partitions.when
Removes all options from Attributes.
The snapshot files for the publication are maintained in the default folder. When AltSnapshotFolder.is not specified, you must specify an alternate location for the snapshot files using
The FlagsAttribute option, which allows a bitwise combination of enumeration values.enumeration supports the
This namespace, class, or member is supported only in version 2.0 of the .NET Framework.