June 28, 2007 at 1:54 pm
Q: Our sysops group is planning to change the names of the SQL Servers located in our Disaster Recovery site (now in it's own new network domain) to be the same as the production server names.
Does anybody have experience with this setup? Are there any gotchas to the envisioned remedy of using fully-qualified names everywhere? What else will we need to make sure to do?
Any advice is appreciated, thanks.
July 2, 2007 at 1:56 am
No problems would incur if you have the application also setup at the DR site so that the application can be brought up along with the DB.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 2, 2007 at 11:28 am
If it's a cold site (no connectivity back to the existing site) or if connectivity where name resolution comes into play is prohibited, there shouldn't be any significant issues.
However, if you have applications which use the network service to connect to other servers, such as Microsoft's CRM 3.0 product, there may be an issue. This is because the computer account in Active Directory is what is seen as connecting and unless their doing a restore of the Active Directory database, simply creating a computer account with the same name will result in a different GUID/SID. These won't match up connecting into SQL Server because of the GUID/SID difference between what is now in the directory and what is stored in the sysxlogins/sys.server_principals system views.
K. Brian Kelley
@kbriankelley
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply