July 11, 2011 at 9:03 pm
I have 7 merge publications and 21 subscriptions between them. I made a change to an article's schema_options in one of the publications and possibly a publication-level change as well, but don't remember. This was using SSMS (it's a 2008 SQL Publisher). After I was done making whatever changes I made, ALL subscriptions - even to other publications - I hadn't touched suddenly were flagged for re-initialization. Some did not. The publications that had that article were the ones that waned to reinit. Unless I'm reading the documentation incorrectly (BOL, TechNet, etc.) I don't see where it is mentioned that any changes, to article or publication, would cause this to happen (ALL publications wanting to reinit, in addition to the one you made the change to). Does anyone know otherwise?
July 12, 2011 at 9:33 am
No guarantees. SSMS will generally do things you dont expect and from experience it will almost always force a reinitialisation when making a publication change of any kind. If you must use ssms, use it to generate scripts (carefully) and qa them before you run them yourself.
I NEVER use ssms to change replication as its far too risky. Stick to TSQL.
July 12, 2011 at 12:02 pm
Thank you MysteryJimbo. I think I learned that last week, the hard way. Still, it'd be nice to find concrete documentation either way.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply