Renaming cluster

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
"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.
|||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...
>