January 23, 2012 at 5:59 am
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?
January 23, 2012 at 6:07 am
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?
January 24, 2012 at 6:40 am
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.
January 24, 2012 at 6:46 am
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.
January 24, 2012 at 7:02 am
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
January 24, 2012 at 7:44 am
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...
January 24, 2012 at 7:48 am
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.
January 25, 2012 at 7:21 am
Thank you for all the tips. The rename was successful!!
January 25, 2012 at 9:37 am
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?
January 16, 2014 at 9:19 pm
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
January 16, 2015 at 1:04 pm
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
Viewing 11 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy