To
verify the name change, simply check the results of SELECT @@SERVERNAME; it should show
the new name.
If this method of renaming a server to make it the new primary server seems a bit out
of date, that??™s because it is. SQL Server 2005 should be able to handle this itself, shouldn??™t
it? The need for that internal server really should be obsolete, given all of the new features
available. The problem is that there are still a lot of backward compatibility issues for
Microsoft to consider when putting out new releases of the product. I could attempt to
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 168
analyze every possible dependency on the internal @@SERVERNAME property, but I only have
one lifetime. It??™s much safer to just assume the worst. Hey, I??™ve said that before, haven??™t I?
Another potential problem with the server-name/IP-change technique is one of IP
routing. I won??™t even pretend to be an expert on network internals, but I am beyond the
neophyte role. Your firewalls may be open to the proper IP address, but it may take some
time before that IP address is associated with the new machine.
Pages:
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330