June 5, 2013 at 10:49 am
We have a single SQL Server running 2 named instances (no default instances) and one is running on SQL Server 2005 and the other SQL Server 2008R2. We did this because we were going thru a transitionary period upgrading our primary accounting DB from SQL 2005 to SQL 2008R2 and we had but one server to use so SQL 2005 and SQL 2008R2 were installed. This has worked well for us over the last few months but now it’s time to move to an updated server on a new SANS.
The server that hosts these 2 versions of SQL Server is a VMWare instance and so we have 2 choices for moving to the new SANS.
1) We can either move the entire VM instance so that when its all done the same 2 instance names are back up and running and to the any client/user everything is the same as far as the login credentials for SQL Server.
OR
2) We can setup a new VMWare instance on the sans, install just SQL Server 2008R2 and then move the DB from the old server to the new.
The benefit to #2 is we get rid of SQL Server 2005 which we no longer need and we start anew (i.e. some of the OS level stuff can be changed per the IT Admins). The downside is that we’d have a new instance name and so anything and everything that has the SQL Server Name/Instance hard coded (and there are quite a few both internal and external to our network) would have to be changed/updated to new instance name.
The benefit to #1 is no changes to any client/user/service that connects to the DB would need to be updated. The downside is we aren’t moving forward.
Aside form using the SQL Utility to create aliases on every client computer, Does anyone have any suggestions on how I can do the best of both worlds, setup a new SQL Server 2008 R2 instance and when it comes time to go live I can have all users/clients that were connecting to the current SQL Server will then connect to the new ine without having to change any of their SQL specific connection settings such as SQL Server Name/Insatnce?
Thanks
Kindest Regards,
Just say No to Facebook!June 5, 2013 at 10:52 am
Google DNS aliasing (or something like that). You can create a DNS alias that points the old server name to the new server. As you deploy new systems you can have those use the new server name but you don't have to make changes to existing systems.
June 5, 2013 at 11:08 am
Lynn Pettis (6/5/2013)
Google DNS aliasing (or something like that). You can create a DNS alias that points the old server name to the new server. As you deploy new systems you can have those use the new server name but you don't have to make changes to existing systems.
Thanks Lynn
Kindest Regards,
Just say No to Facebook!June 5, 2013 at 11:38 am
You can set up an alias on the client (SQL Native Client) via the client configuration tool.
The probability of survival is inversely proportional to the angle of arrival.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply