Disabling replication leaves "junk" behind

  • Hi,

    I had a simple replication setup between 2 servers, just testing for the moment. Transactional Push from Publisher to Subscriber.

    To clean up and start again, I ran the Disable Publishing and Distribution Wizard on the Publisher which seemed to do its thing OK, except that I noticed some "junk" left on the subscriber to the tune of Subscription entries that had not been deleted. I also couldn't delete the table from the former subscriber because SQL thought that it was still involved in replication.

    Should I have deleted the subscription from the subscriber before disabling Publishing at the Publisher or is there something else I should also do?

    TIA

  • The short answer is Yes.

    Always remove the subscriptions first, otherwise you can end up with a very annoying situation because SQL Server sees the database still as part of a replication. You then have to clean up everything manually, which means editing systemtables. Be very carefull!!!

    [font="Verdana"]Markus Bohse[/font]

  • Thought so, thanks for the confirmation.

    I've actually already tried cleaning out the system tables, but despite visiting everywhere that I thought I should, it still wouldn't go away. Fortunately, this is only a small development server so I'm about to re-install SQL which should do the trick.

  • You might want to check out this article

    http://www.mssqlserver.com/replication/bp_manual_replication_cleanup.asp

    [font="Verdana"]Markus Bohse[/font]

  • Legend, great tip, thanks very much for the pointer.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply