Bulk dematerialization is invoked using the without purge option of the drop subscription command. The subscription status becomes Dematerializing at the replicate Replication Server and a drop request is forwarded to the primary Replication Server.
When the primary Replication Server receives the drop request, it stops sending updates for the subscription to the replicate Replication Server. The subscription status becomes Dematerializing at the primary Replication Server and a drop request is returned to the replicate Replication Server.
When the replicate Replication Server receives the drop request, the subscription status is changed to Removing at the replicate. The replicate Replication Server logs in to the primary Replication Server and requests that it delete the subscription from its system tables. When that request has succeeded, the replicate Replication Server removes the subscription from its own system tables and the dematerialization is complete.