If I had to do this, "replicate several hundred databases from a half dozen SQL servers", I'd just create a script to write out the replication TSQL commands and execute...

Without more information it is hard to be sure, but I'd suspect that your distribution database is on the same SAN infrastructure as your publisher. We also use a...

Toby White (11/2/2009)

---

Even though A is empty string versus Null the answer is still obvious given that it is multiple choice. In other words it was obvious that the author...

I think what you need is some more quotes:

NOT

"INSERT INTO tblDate (myDate , WorkerNum) VALUES ( ' + d + ',

'" + workerNum + "')"

BUT

"INSERT INTO tblDate (myDate , WorkerNum)...

Submit something like this to SQLCMD:

SET NOCOUNT ON;

:XML ON

SELECT COL1,COL2

FROM [SBA].DBO.[TABLE1]

FOR XML RAW, ROOT('DATA')

So, from a Command window;

SQLCMD -i "C:\PathAndFileNameOfAboveScript" -o "C:\PathAndFileNameForOuput"

I just finished discovering the same, that by using nodes and value I can correctly get the values back with leading blanks. Apparently OPENXML does some automatic "cleansing" of...

So, as a follow up, what about a more complex situation:

Clustered default instance of SQL Server with different virtual IP address and network name then the virtual name and address...

I'd probably add a step at the end.

After the applications are up and you're sure they're all pointed at the new server and working fine, bring the old database back...

I would have ranked this article higher if you hadn't included the "red herring" of mentioning Broker Services. I saw no mention that the CREATE DATABASE ... FOR ATTACH...

Post snapshot scripts are not an option due to the fact we don't have snapshot initialization.

We were manually running the procedure to create the custom procs after deploying replication, but...

"How are you calling..."

Not sure if this is of any use, but...

To register the custom proc, this snippet is part of a command script (hence the variable syntax) we use...

I see that CDC is designed to "share" log reading with replication. Does anyone know if this still works when you are using a remote Distributor? Wouldn't having...

If it is only a record or few, just delete the duplicate from the subscriber database(s) and then replication will resume. Continue this until all duplicates are handled.

If your...

Remove the replication "programmatically" by calling the system stored procedures directly. This in outlined in BOL:

Stop all replication-related jobs. For a list of job names, see the "Agent Security...

You could create a cross-domain trust relationship which would allow the logon the agent is using in your domain to have privileges in the target domain. This would typically...