Transactional Replication is messed up

  • Hi,

    I had to refresh the development dbs from production backups. I did not realize that production dbs are replication to the reporting server. At the same time development dbs are replicated to the development reporting servers.

    Now replication in development is totally messed up.

    I was able to cleanup the subscriptions from development reporting servers(subscriber) using sp_subscription_cleanup procedure.

    I ran sp_removedbreplication form the databases at the publisher in the developemnt environment.

    I don't see anything under local publications but when I launch the replication monitor, I see a bunch of databases listed for replication but no status.

    I would like to cleanup replication completely in development and start it from scratch. What commands or updates should I run to clean this up?

    I also would like to know how to cleanly refresh the databases from production to development in future since both the environments are replicated?

    Thanks,

    Shaili

  • Hi Shaili,

    As a former Microsoft employee I hate to say this but removing replication has always been a bit of headache.

    Did you try to follow all the steps outlined in http://support.microsoft.com/kb/324401 "How to manually remove a replication in SQL Server 2000 or in SQL Server 2005"? (without jumping to the shortcut at the end 🙂 ).

    HTH!

    /Elisabeth

    elisabeth@sqlserverland.com
    MCITP | MCT
    http://sqlblog.com/blogs/elisabeth_redei/
    http://linkedin.com/in/elisabethredei

Viewing 2 posts - 1 through 1 (of 1 total)

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