Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
up vote 1 down vote favorite

I believe the steps necessary would be:

  1. Generate scripts to "create or enable" (including replication jobs) by right clicking the subscription in question in "local subscriptions" and saving the file generated.
  2. Delete the replication on the subscribing side.
  3. Backup the subscribed database
  4. Restore the subscribed database
  5. Run generated script to restore replication

I'm afraid I'm missing something here. E.g.: There exists a backlog of existing replication files. Will they disappear all by themselves once all subscribers are removed? etc.

share|improve this question
Not sure what you mean but 'Stuck'? I have had broken replication that took quite a bit of work to get it fully removed before I could reestablish replication. Using sp_removedbreplication<database name> is one of the steps but have also had to use sp_removesrvreplication on more troublesome cases and on the worst cases, I had to go in and remove all of the replication triggers/views/sprocks – user1207758 Oct 16 '12 at 20:22
By stuck I meant that someone had altered the database in a way that could not be automatically replicated. – Erik Itland Oct 17 '12 at 20:23

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.