| Groups | Blog | Home |
sql server clustering : Renaming cluster
older server running SQL 2000. We also have a MSCS cluster that we've built which is running SQL 2005. We want to get all the databases on the SQL 2005 cluster and retire the SQL 2000 server. Is there any way to rename the cluster? It seems to me that the easiest way would be to restore the databases from 2000 to 2005, take down the 2000 machine, rename the 2005 cluster to have the same name as the old SQL 2000 server and we're done. The other option is to bring down the 2000 server, but keep the 2005 machine with the new name - problem is there's a lot of old code that has the connection strings hardcoded. It was suggested that we could do a DNS pointer to resolve the old server name to the new name, but that didn't seem to work with all of the apps that we've tested.... Any suggestions?? I haven't been able to find much advice on how to do a 2000 to 2005 upgrade when you're also switching servers. Thanks for your
That was the original plan. We did this in a test environment - old java
code we have that uses JDBC wasn't able to resolve the server name. Also, a ..net service that we tested didn't resolve the name correctly, either, which is why I thought it wasn't going to work out. Perhaps there was a separate isue with that service when we tested it. As far as you know, the DNS solution should work pretty well? Are there any "got'chas" or other downsides I should keep in mind? Thanks for your time. [quoted text, click to view] "Geoff N. Hiten" wrote:
> Why bother renaming? Create a DNS SRV record repointing the old name to the > new server/instance. > > -- > Geoff N. Hiten > Senior SQL Infrastructure Consultant > Microsoft SQL Server MVP > > > "Morgan" <Morgan@discussions.microsoft.com> wrote in message > news:66673D99-7035-491D-87EA-A10DE2A89FEB@microsoft.com... > >I am looking for some help with a SQL Upgrade that we are doing. We have > >an > > older server running SQL 2000. We also have a MSCS cluster that we've > > built > > which is running SQL 2005. We want to get all the databases on the SQL > > 2005 > > cluster and retire the SQL 2000 server. > > > > Is there any way to rename the cluster? It seems to me that the easiest > > way > > would be to restore the databases from 2000 to 2005, take down the 2000 > > machine, rename the 2005 cluster to have the same name as the old SQL 2000 > > server and we're done. > > > > The other option is to bring down the 2000 server, but keep the 2005 > > machine > > with the new name - problem is there's a lot of old code that has the > > connection strings hardcoded. It was suggested that we could do a DNS > > pointer to resolve the old server name to the new name, but that didn't > > seem > > to work with all of the apps that we've tested.... > > > > Any suggestions?? I haven't been able to find much advice on how to do a > > 2000 to 2005 upgrade when you're also switching servers. Thanks for your > > time. >
Why bother renaming? Create a DNS SRV record repointing the old name to the
new server/instance. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP [quoted text, click to view] "Morgan" <Morgan@discussions.microsoft.com> wrote in message
news:66673D99-7035-491D-87EA-A10DE2A89FEB@microsoft.com... >I am looking for some help with a SQL Upgrade that we are doing. We have >an > older server running SQL 2000. We also have a MSCS cluster that we've > built > which is running SQL 2005. We want to get all the databases on the SQL > 2005 > cluster and retire the SQL 2000 server. > > Is there any way to rename the cluster? It seems to me that the easiest > way > would be to restore the databases from 2000 to 2005, take down the 2000 > machine, rename the 2005 cluster to have the same name as the old SQL 2000 > server and we're done. > > The other option is to bring down the 2000 server, but keep the 2005 > machine > with the new name - problem is there's a lot of old code that has the > connection strings hardcoded. It was suggested that we could do a DNS > pointer to resolve the old server name to the new name, but that didn't > seem > to work with all of the apps that we've tested.... > > Any suggestions?? I haven't been able to find much advice on how to do a > 2000 to 2005 upgrade when you're also switching servers. Thanks for your > time.
DNS refresh times (and Active Directory sync times if you are integrating
the two) can bite you. Use PING and NSLookup on your client systems to validate DNS name resolution. Also, some old JDBC drivers still use DBLib calls. You will have to upgrade those drivers to an ODBC or OLEDB based driver. I have used this technique extensively in migrations and it works very well as long as the clients don't hard-code an IP address. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP [quoted text, click to view] "Morgan" <Morgan@discussions.microsoft.com> wrote in message
news:71BCCD7B-AB82-46BF-A1FB-F3D96484E85D@microsoft.com... > That was the original plan. We did this in a test environment - old java > code we have that uses JDBC wasn't able to resolve the server name. Also, > a > .net service that we tested didn't resolve the name correctly, either, > which > is why I thought it wasn't going to work out. Perhaps there was a > separate > isue with that service when we tested it. As far as you know, the DNS > solution should work pretty well? > > Are there any "got'chas" or other downsides I should keep in mind? > > Thanks for your time. > > "Geoff N. Hiten" wrote: > >> Why bother renaming? Create a DNS SRV record repointing the old name to >> the >> new server/instance. >> >> -- >> Geoff N. Hiten >> Senior SQL Infrastructure Consultant >> Microsoft SQL Server MVP >> >> >> "Morgan" <Morgan@discussions.microsoft.com> wrote in message >> news:66673D99-7035-491D-87EA-A10DE2A89FEB@microsoft.com... >> >I am looking for some help with a SQL Upgrade that we are doing. We >> >have >> >an >> > older server running SQL 2000. We also have a MSCS cluster that we've >> > built >> > which is running SQL 2005. We want to get all the databases on the SQL >> > 2005 >> > cluster and retire the SQL 2000 server. >> > >> > Is there any way to rename the cluster? It seems to me that the >> > easiest >> > way >> > would be to restore the databases from 2000 to 2005, take down the 2000 >> > machine, rename the 2005 cluster to have the same name as the old SQL >> > 2000 >> > server and we're done. >> > >> > The other option is to bring down the 2000 server, but keep the 2005 >> > machine >> > with the new name - problem is there's a lot of old code that has the >> > connection strings hardcoded. It was suggested that we could do a DNS >> > pointer to resolve the old server name to the new name, but that didn't >> > seem >> > to work with all of the apps that we've tested.... >> > >> > Any suggestions?? I haven't been able to find much advice on how to do >> > a >> > 2000 to 2005 upgrade when you're also switching servers. Thanks for >> > your >> > time. >> >>
Hi
The next link explain how to change the name in a SQL2005 cluster, but have some issues, read the document http://msdn2.microsoft.com/en-us/library/ms178083.aspx Another option is ... -- uninstall SQL 2005 from the new cluster, -- (optional) upgrade the sql 2000 cluster to SQL 2005, -- turn off the upgraded sql 2005, -- if you have a SAN, in the new cluster set the same drives name as your old SQL 2000 cluster -- Install the new sql 2005 cluster using the same drives and routes as the old cluster -- After SQL 2005 is OK, backup the new master, model and msd. -- then take off line the new sql server 2005 service, and copy all mdf , ldf and folders from the old cluster, important, the same folder names and drives names and will work again.. [quoted text, click to view] "Morgan" wrote:
> I am looking for some help with a SQL Upgrade that we are doing. We have an > older server running SQL 2000. We also have a MSCS cluster that we've built > which is running SQL 2005. We want to get all the databases on the SQL 2005 > cluster and retire the SQL 2000 server. > > Is there any way to rename the cluster? It seems to me that the easiest way > would be to restore the databases from 2000 to 2005, take down the 2000 > machine, rename the 2005 cluster to have the same name as the old SQL 2000 > server and we're done. > > The other option is to bring down the 2000 server, but keep the 2005 machine > with the new name - problem is there's a lot of old code that has the > connection strings hardcoded. It was suggested that we could do a DNS > pointer to resolve the old server name to the new name, but that didn't seem > to work with all of the apps that we've tested.... > > Any suggestions?? I haven't been able to find much advice on how to do a > 2000 to 2005 upgrade when you're also switching servers. Thanks for your
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |