Requirements for Creating Subscriptions

Learn what permissions you require before you can create subscriptions.

A subscription creator must have accounts on both the primary and replicate Replication Servers, and the accounts must have the same login name and password. The subscription creator enters a command or a series of commands at the replicate Replication Server, which passes the request to the primary Replication Server.

When the optional clauses use dump marker and subscribe to truncate table are used, the login name and password for the replicate Replication Server should be the same for the primary Replication Server, as well as for both the primary and replicate databases.

At the replicate Replication Server (the destination of the subscription data), the subscription creator must have, at minimum, create object permission in order to materialize the subscription.

At the primary Replication Server (the source of the subscription data), the subscription creator must have, at minimum, primary subscribe permission in order to enter at the replicate site all commands involved in creating subscriptions:

create subscription (for atomic and nonatomic materialization)
define subscription (for bulk materialization)
activate subscription (for bulk materialization)
validate subscription (for bulk materialization)
drop subscription

The primary subscribe permission, a subset of create object permission, is provided at the primary Replication Server. It lets users at replicate sites create subscriptions to data stored at primary sites. From replicate sites, these users cannot create any other objects at primary sites, only subscriptions.

Note: Users with create object and sa permissions can also create subscriptions from replicate Replication Servers. The minimal permission required at the primary Replication Server for a user at a replicate site to create subscriptions is primary subscribe.

A user creating a subscription must have the following Adaptive Server permissions:

select permission on the table in the primary database
insert, update, and delete permission on the replicate table
execute permission on the rs_marker stored procedure in the primary database

If you are a replication system administrator, restrict primary subscribe and create object permissions at primary sites to users who require them in order to create subscriptions.

It is possible for a user who has primary subscribe or create object permission to begin creating a subscription without having select permission on the table. If this occurs, Replication Server responds in the following manner:

If the subscription is created with atomic materialization, the select with holdlock operation fails at the primary database during materialization. The subscription retry daemon (dSUB) retries the select with holdlock until the subscription is dropped or until the select permission is granted to the user for the table at the primary database.
If the subscription is created with nonatomic materialization, the select operation fails at the primary database during materialization. The subscription retry daemon (dSUB) retries the select until the subscription is dropped or the select permission is granted.
If the subscription is created with bulk materialization, there is no select transaction, so no error messages are logged, and the subscription succeeds.