March 19, 2009 at 7:35 am
When you say script 'everything', there are caveats there: If there are pull subscriptions, they are scripted on other systems than the publisher. Even with push subscriptions, you still have entries on the subscriber machines that you have to account for.
Some of the warning messages that SQL Server displays are generic, built into the maintenance process. Others may be specific to reading the settings stored in the server. For those not immersed in replication, there's no good way to tell when a warning message is generic, and when it's specific to their situation (even when it's generic!).
March 19, 2009 at 1:16 pm
steve smith (3/19/2009)
When you say script 'everything', there are caveats there: If there are pull subscriptions, they are scripted on other systems than the publisher. Even with push subscriptions, you still have entries on the subscriber machines that you have to account for.Some of the warning messages that SQL Server displays are generic, built into the maintenance process. Others may be specific to reading the settings stored in the server. For those not immersed in replication, there's no good way to tell when a warning message is generic, and when it's specific to their situation (even when it's generic!).
Steve
I manage a very large number of publications and all is done through scripts.
We don't use the UI to touch replication settings.
It becomes trivial to use our scripts because there is a lot of standardization going on under the hood.
All locations, schema_options and properties are standard and once we get to that point is "trivial" to mange replication.
I do understand what you are trying to do. But you will definitely find all kinds of issues as well with ***many*** UI features, not just replication.
* Noel
March 19, 2009 at 3:16 pm
Noel, I'm old school. Give me a command line any day. I've constantly exasperated with the inability to get at the underlying coding that goes into so many UI modules these days. I still remember walking through the line-by-line debugs in VB 6, and amazed at how verbose it seemed, before anything even happened. A far cry from APL, where a well formed program could be one line of code.
However, when you are creating a 'basic' snapshot replication with no fancy idiosyncrasies, the UI gets you there quickly and safely. It's just hard to go back and then find out what was done to set it up, because there are no scripts to refer to, and how do you know you've generated everything you need?
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply