Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
steelkilt
Constraint Violating Yak Guru
255 Posts |
Posted - 2009-06-12 : 11:41:22
|
Hello. I am facing a deadline to migrate my Windows 2000 server (running SQL Server 2000) to a new domain. I have been instructed to join the new domain first -- a very straightforward process -- and then rename my SQL server since the existing SQL server name will not be recognized once the new domain is joined.I have looked at books online and there is a discussion of renaming a server, but I don't see info that addresses my specific situation.Joining a new domain will result in the following change:old Win 2k server name: MYSERVER.olddomain.something.govnew Win 2k server name: MYSERVER.newdomain.govMYSERVER is the current name of my sql server 2000 default installation. No named instances, just one installation.I was under the impression that the SQL Server name is simply MYSERVER, but the IT brass informs me that when I rename the SQL server I must use the long domain name. Can someone clarify whether this is so and perhaps provide a link to the procedure?Finally, I have a website using a server-based DSN as well as various users who have DSN connections on their desktops, all pointing to the SQL server MYSERVER. Once the domain migration is complete, I'm assuming the transition will be seamless for my end users since the base server name will not change.All URLs in my code refer to the DNS http://MYSERVER/etc...thanks! |
|
|
|
|