I'm trying to implement Merge Subscriptions between two servers. The question is, how can I programmatically remove the subscription information from the subscriber?

I can call sp_dropmergesubscription at the Publisher but this does not affect the Subscriber server. Deleting rows from the sysmergesubscriptions, sysmergearticles, and sysmergepublications tables will remove the subscription item in the server's Replication folder.

There is a dependency between each replicated table and a set of system sprocs/triggers, all of which I can remove programmatically. I've can also drop rows from MSmerge_replinfo and MSmerge_genhistory.

However, even after doing this I am unable to drop the table despite there being no apparent dependencies.

Can anyone help? I would have thought this would be a fairly common task - surely at least as common as removing a subcription on the publisher side, which warrants its own system sproc.

Thanks

I havn't had much success at that either. the only way I was able to do it was to disable replication and then re-enable it which is fine if thats the only database your replicating. If you hear of another way let me know!
David

I've cracked it!

There is a stored procedure sp_mergesubscription_cleanup which should be run against the subscription database at the Subscriber. This does what it says on the tin, allowing the replicated articles to be dropped at the subscriber without complaint.

And why did it take so long for me to find this out? Well apart from the Books Online not actually referring to this sproc when dealing with sp_dropmergesubscription and the Publisher side of things, when I finally found that sp_mergesubscription_cleanup even existed the help files specify that it should be run at the Publisher!!!

Note that there is another sproc called sp_subscription_cleanup which I guess is the equivalent for snapshot and transactional replication. Books Online gets it correct for this one, specifying it should be run at the Subscriber.