deactivate subscription subscription_name
for {table_repdef_name | func_repdef_name |{publication pub_name |
database replication definition db_repdef_name}
with primary at dataserver.database}
with replicate at dataserver.database
go
After you deactivate the subscriptions, Replication Server does not propagate all the transactions in the inbound queue to the outbound queue of the in-memory or relaxed-durability database.
In contrast, when you drop a subscription, all the committed transactions that have been written into the inbound queue are distributed downstream of Replication Server. You can deactivate a subscription even if the DSI is not running because the deactivation only happens at the primary site. When the deactivate marker arrives at the outbound queue, you can see this entry in the Replication Server log:
The deactivate marker for subscription subscription_name arrives at outbound queue: data_server_name.database_name.
After the deactivate marker arrives at the outbound queue, use sysadmin sqm_purge_queue to purge the outbound queue at the replicate site to quickly empty the outbound queue. See Replication Server Reference Manual > Replication Server Commands > sysadmin sqm_purge_queue.