August 18, 2011 at 10:24 am
Hello everyone...
I had a scenerio this morning where I needed to restore the production database to qa. Well it turns out this database had some replication on some of the objects. I generated scripts of all publishers, then delete the publishers. This did not delete the subscriptions on the subscriber side like I thought it would, so I deleted them manually on the subscriber/distributer sql.
Then I restored the database and ran the scripts to re-create the publisher. I then ran the re-initialization to get replication back going. The initialization failed becuase objects did not exist.
I was under the impression that a new snapshot sent via initialization would overwrite was was on the subscriber with all new data from the publisher. Well it looks like it just tries to merge the changes.
My question is how would you have handled this situation to avoid issues?
August 18, 2011 at 11:39 am
Were you trying to get rid of and rebuild the replication on the production server or the QA server? You lost me on that point.
When I restore a replicated database from prod to test/QA/dev/whatever, I don't mess with the replication settings on production, and just kill the replication in dev, or re-build it in QA (but with different subscribers), since QA should parallel production as much as possible.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
August 21, 2011 at 8:28 am
sqlsponge2 (8/18/2011)
I was under the impression that a new snapshot sent via initialization would overwrite was was on the subscriber with all new data from the publisher.
You are correct in so far as it is the default action. When added the article to a publication you can change this behaviour.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply