Use drop subscription to drop a publication subscription and all of its article subscriptions, or to drop a single article subscription.
drop subscription removes information about the publication subscription and its article subscriptions from system tables at the source and destination servers. It does not remove publication information from the destination server. Thus, you can create another subscription against the publication, and Replication Server only needs to reload primary site information if it has been changed.
Include the without purge clause to retain existing rows replicated by the subscription to the destination database. The subscriptions are dropped all at once.
This example drops a subscription named pubs2_sub for the publication pubs2_pub using without purge.
drop subscription pubs2_sub for publication pubs2_pub with primary at TOKYO_DS.pubs2 with replicate at SYDNEY_DS.pubs2 without purge
Include the with purge clause to delete existing rows replicated by the subscription to the destination database. The subscriptions are dropped one at a time.
This example uses with purge:
drop subscription pubs2_sub for publication pubs2_pub with primary at TOKYO_DS.pubs2 with replicate at SYDNEY_DS.pubs2 with purge
The following example deletes the article pubs2_art, without removing rows replicated by the subscription.
drop subscription sub for article pubs2_art with primary at TOKYO_DS.pubs2 with replicate at SYDNEY_DS.pubs2 without purge
Refer to Chapter 3, “Replication Server Commands,” in the Replication Server Reference Manual for complete syntax and usage guidelines.
