Server being replaced moving to new Data Center - New Name
-
I have a Server that is being replaced moving to new Data Center with a New Name.
There are Excel Documents with Data Connections and a ton of Access Database with links to the old server.
Then I have a lot of SSIS Packages that have the Connection information hard coded.
Can I leverage a SQL Server Alias, DNS Entry to redirect, etc to minimize the impact of the move?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/ -
Welsh Corgi (1/16/2012)
I have a Server that is being replaced moving to new Data Center with a New Name.There are Excel Documents with Data Connections and a ton of Access Database with links to the old server.
Then I have a lot of SSIS Packages that have the Connection information hard coded.
Can I leverage a SQL Server Alias, DNS Entry to redirect, etc to minimize the impact of the move?
I think if you can use DNS forwarding it may minimize the impact. I used DNS forwarding for Disaster Recovery in combination with Log Shipping. As long as the Instance names and ports are the same on the new Server I think it may minimize the impact.
-
We are in the habit of creating an alias for the SQL Server name so when the hardware is replaced all we do is simply point the dns alias to the new servername and bingo no one has to touch a connection at all.
-
Markus (1/18/2012)
We are in the habit of creating an alias for the SQL Server name so when the hardware is replaced all we do is simply point the dns alias to the new servername and bingo no one has to touch a connection at all.The new Server is already up so can I still use the Alias approach?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/ -
Yes you can. Simply move everything however you plan on doing it. Then once the original servername is off the network have the dns alias of the same name created pointing to the IP address of it now. You might have to reboot servers that make connections to the SQL Server so it can see the name with the new IP address.
-
Markus (1/18/2012)
Yes you can. Simply move everything however you plan on doing it. Then once the original servername is off the network have the dns alias of the same name created pointing to the IP address of it now. You might have to reboot servers that make connections to the SQL Server so it can see the name with the new IP address.Thanks. If you know of any articles that provide step by step instructions, I would appreciate it.:-)
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/ -
Post moved to the following URL:
http://www.sqlservercentral.com/Forums/Topic1238156-146-1.aspx[/url]
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/ -
What I was talking about was creating a dns alias on the Windows network domain... not a SQL Server created alias.....
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply