Post reply

Transaction Replication is messed up.

  • November 4, 2008 at 10:42 am

    #127552

    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

  • November 4, 2008 at 1:06 pm

    #893849

    Any help please??

  • November 4, 2008 at 2:58 pm

    #893920

    Your db's syspublications and syssubscriptions were lost, or had the prod's copy when you restored it with keep_replication and your distribution db still has the dev's publication/subscription info.

    Do you have all the replication scripts (publication and subscriptions in dev)?

    If you still have a backup of your db in dev, try restoring it, then delete the subscriptions and publications. Then restore the prod copy and recreate the publication and subscriptions from your replication script.

    _____________
    Donn Policarpio

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

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