Denesh Naidoo (12/9/2013)
Hi All,Currently we have a stand alone SQL Server 2008 R2 Ent server. We are planning to move this environment to a Cluster. Once the cluster is ready...the plan is as follows:
1. Copy user databases to the cluster
2. Restore Master and MSDB from stand alone to cluster
My concern is the Server and SQL names. So...the Stand Alone server is called ServerA. When we build the cluster...the name will be ServerB...which we are happy with (not having the same name as the current server). Once I do a restore...we will have the servername = ServerB...but the SQL name
(select @@servername) will be ServerA. I then plan to run the SP_dropserver sp_Addserver to change the SQL name from ServerA to ServerB.
I've done this on a standalone server and it works fine...I just wanted to check if they might be issues with a cluster.
You cannot perform this, the "IsClustered" option will be set to false in the stand alone system database. You must script out any objects required (you can do most of this in advance) and move them to the new instance. As your service account and computernames will likely change you'll possibly encounter issues with the service master key too, you have been warned :exclamationmark: :exclamationmark:
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉