Re: Renaming cluster

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




"Morgan" <Morgan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:71BCCD7B-AB82-46BF-A1FB-F3D96484E85D@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:66673D99-7035-491D-87EA-A10DE2A89FEB@xxxxxxxxxxxxxxxx
>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.



.

Relevant Pages

  • Re: N+1 Configuration
    ... Jasper Smith (SQL Server MVP) ... But looking in the cluster admin tool, ... mounting all other drives under that drive ...
    (microsoft.public.sqlserver.clustering)
  • Re: Clustering Question
    ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... Do you want to cluster SQL? ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)
  • Re: issue with DC replication
    ... Are the addresses in the same network ID as the FTP servers? ... different AD-I DNS server ip address which will provide the DNS services. ... Well, if it fails when DC1 is down, that means that for some reason DC2 is not responding to the server requests when DC1 is down (also check if both ... >> have 2 DCs that are supporting that cluster? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clustering Question
    ... The SQL Cluster would need to be ... SQL will need to Enterprise as well. ... So if I understand you correctly one computer will need Windows Server ...
    (microsoft.public.windows.server.clustering)
  • Re: issue with DC replication
    ... different AD-I DNS server ip address which will provide the DNS services. ... I think that when you lose resolution between the FTP and the DNS/DC ... You have one FTP cluster in Active/Passive configuration? ...
    (microsoft.public.windows.server.active_directory)