Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

REVOKE PUBLISH statement [SQL Remote]

Use this statement to terminate the identification of the named user ID as the CURRENT publisher.

REVOKE PUBLISH FROM userid

Each database in a SQL Remote installation is identified in outgoing messages by a publisher user ID. The current publisher user ID can be found using the CURRENT PUBLISHER special constant. The following query identifies the current publisher:

SELECT CURRENT PUBLISHER;

The REVOKE PUBLISH statement ends the identification of the named user ID as the publisher.

You should not REVOKE PUBLISH from a database while the database has active SQL Remote publications or subscriptions.

Issuing a REVOKE PUBLISH statement at a database has several consequences for a SQL Remote installation:

• You will not be able to insert data into any tables with a CURRENT PUBLISHER column as part of the primary key. Any outgoing messages will not be identified with a publisher user ID, and so will not be accepted by recipient databases.

If you change the publisher user ID at any consolidated or remote database in a SQL Remote installation, you must ensure that the new publisher user ID is granted REMOTE permissions on all databases receiving messages from the database. This will generally require all subscriptions to be dropped and recreated.

Must have DBA authority.

Automatic commit.

• GRANT PUBLISH statement [SQL Remote]
• REVOKE REMOTE statement [SQL Remote]
• REVOKE REMOTE DBA statement [SQL Remote]
• REVOKE CONSOLIDATE statement [SQL Remote]

• SQL/2003    Vendor extension.

REVOKE PUBLISH FROM publisher_ID;