SQL Failover Cluster Rename?

Question

Post reply

SQL Failover Cluster Rename?

mikel 98376

Mr or Mrs. 500

Points: 581
More actions
January 23, 2012 at 5:59 am

#391374

I currently have a SQL Failover Cluster that I am looking into renaming, so that I can change the FQDN. Currently my SQL instance has the same name as the "SQL Network Name" property. Does this have to match - or will it be ok to change the SQL Network name but leave this instance?

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Robert Murphy UK1 Default port Points: 1455 More actions · Answer 1

Renaming the virtual server name is no problem:

http://msdn.microsoft.com/en-us/library/ms178083.aspx

As for renaming the instance name itself, this is not possible as far as I can see, or it is by changing all sorts of registry keys, you may be better off reinstalling unless someone else here has some better advice?

Robert Murphy, Microsoft MCITP (Database Administrator 2008) and MCAD Certified

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 2

You probably should open a ticket with Microsoft about renaming a cluster. You could open up a whole can or worms on that one. If you have the hardware and storage you would be safer to reinstall and backup/restore to it.

mikel 98376 Mr or Mrs. 500 Points: 581 More actions · Answer 3

Hah - now you tell me. I don't have the hardware or storage to backup/restore a 4+ TB database. So far, the cluster's renamed and it's running - but I can't get into the SQL Configuration Manager - and having issues with my first problem, trying to enable SSL for the SQL instance.

Robert Murphy UK1 Default port Points: 1455 More actions · Answer 4

As I already posted. Did you follow the renaming process as per the documentation from Microsoft:

http://msdn.microsoft.com/en-us/library/ms178083.aspx

Robert Murphy, Microsoft MCITP (Database Administrator 2008) and MCAD Certified

mikel 98376 Mr or Mrs. 500 Points: 581 More actions · Answer 5

Yes, I followed these instructions to a T.

I had to add a little registry hack adding a blank ClusterName key under the MSSQL.2.

If I do: select @@servername, I actually get back the old cluster name. So I think this is more complicated...

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 6

To update the internal servername you need to do this:

sp_dropserver 'oldname'

sp_addserver 'newservername', 'LOCAL'

Once you do this, bounce SQLServer to make it take effect and run the select @@servername. It should be updated now.

mikel 98376 Mr or Mrs. 500 Points: 581 More actions · Answer 7

Thank you for all the tips. The rename was successful!!

mikel 98376 Mr or Mrs. 500 Points: 581 More actions · Answer 8

Ok - maybe not so smoothly. Now all my SSIS packages are failing saying "[Execute SQL Task] Error: Failed to acquire connection "DB_CONNECTION". Connection may not be configured correctly or you may not have the right permissions on this connection. "

I have changed the parameters in the "DB_CONNECTION" to point to the new server, I have clicked "Test Connection" which succeeds, but when I try to run the package in debug mode, it gives the error above. I am confused! Help?

SQLSlack3r SSC-Addicted Points: 428 More actions · Answer 9

For clusters with SSIS running, I always specify the server name in the C:\Program Files\Microsoft SQL Server\110\DTS\Binn\MsDtsSrvr.ini.xml file.

MCSA SQL 2014

Rudy Panigas SSChampion Points: 10702 More actions · Answer 10

Hello,

If you change the name you also need to do the following to update sys.jobs. If you don't you won't be able to modify the jobs.

-- Update the server name in the sysjobs table

update msdb..sysjobs set originating_server = CONVERT(NVARCHAR(30), SERVERPROPERTY('ServerName'))

go

Rudy