Force delete an SQL copy subscription exception

Recently, I have performed Database Synchronization and backup. After I subscribe to the primary database through [copy] provided by SQLService, the subscriber (slave database) cannot determine the subscribe to the slave database because of an exception, just want to clean up, subscribe to re-do synchronization, results ..... Publishing on the master database does not allow deletion. If someone subscribes and cannot contact the slave database, it is very tangled,

Recently, I have performed Database Synchronization and backup. After I subscribe to the primary database through [copy] provided by SQLService, the subscriber (slave database) cannot determine the subscribe to the slave database because of an exception, just want to clean up, subscribe to re-do synchronization, results ..... Publishing on the master database does not allow deletion. If someone subscribes and cannot contact the slave database, it is very tangled,

Recently, I have performed Database Synchronization and backup. After I subscribe to the primary database through [copy] provided by SQLService, the subscriber (slave database) cannot determine the subscribe to the slave database because of an exception, just want to clean up, subscribe to re-do synchronization, results ..... Publishing on the master database does not allow deletion. If someone subscribes and cannot contact the slave database, the sub-database subscription is suspended, and the server space and website space are gone, but the master database still exists, and the release of the master database is not allowed to be deleted. It is hard to solve this problem. I tried N + 1 method (stop the database/separate/directly Delete the database), but it won't work at the end, the system prompts that a subscription is available. deletion is not allowed, and Baidu ~ Baidu ~ Baidu ~ Finally, Baidu finally found a way to force Delete the replication and publishing of the master database without notifying the subscriber (slave database). Of course, the statement is attached to the Hong Kong vm for the next use:

Sp_removedbreplication 'database name' delete database replication/synchronization problems