Pro SQL Server Disaster Recovery

Prev | Current Page 317 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"

If Ockham were alive, I??™d send him an e-mail that
just says, ???THHHHHHHPT.???
When using the rename/IP-change technique, you better be sure to change the internal
name of the SQL Server itself. SQL Server 2000 and 2005 will continue to run almost
everything without changing that internal server name. However, certain functions, such
as replication, will display odd behavior. (I won??™t elaborate on the exact behaviors I??™ve
encountered, because this is supposed to be a book, not a four-volume epic tale.)
Changing the name is simple, and I suggest always adding the process to any disaster
recovery documentation:
Sp_dropserver <>
Sp_addserver <>, 'local'
nNote Be sure to reverse all of this once the primary server is restored; otherwise, you??™ll have a nameresolution
conflict on the network between the restored primary server and the secondary server that is
now acting as the primary.
It??™s important to get the 'local' clause in when you add the new server name. The
reason you have to drop the old server name is because it has been flagged as local.

Pages:
305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329

Beginning PHP and MySQL E-Commerce: From Novice to Professional, Second Edition (page 683) Beginners Guide to SQL Server Integration Services Using Visual Studio 2005 (page 67) Professional Windows PowerShell for Exchange Server 2007 Service Pack 1 (page 634)

E-Books for you

James Luetkehoelter

"Pro SQL Server Disaster Recovery"