SQL Server 2000 Virtual Server Renaming

#1

Hi All
Client has decided they want to rename the Virtual SQL Server from
(lets say) SQLA to SQLB.

Fair enough. Uninstall SQL Server and reinstall.

Am I right in thinking that I cannot restore the master from the SQLA
incarnation to the SQLB incarnation.

Clearly I would like to do this because all the user databases are
unchanged and in the same locations and it would save me reattaching
each user database, recreating logins etc etc.

Or can I restore it and then use sp_dropserver, sp_addserver, bearing
in mind its clustered?
Thanks in advance

Barry

#2

You can't move master or restore to a different machine. SQL = Master,
Master = SQL. It just can't be done as far as I know.

Like you also mentioned, its not that though to attach DBs.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering

"BarryLynch" <allspammustdie (AT) yahoo (DOT) com> wrote

Quote:

Hi All
Client has decided they want to rename the Virtual SQL Server from
(lets say) SQLA to SQLB.

Fair enough. Uninstall SQL Server and reinstall.

Am I right in thinking that I cannot restore the master from the SQLA
incarnation to the SQLB incarnation.

Clearly I would like to do this because all the user databases are
unchanged and in the same locations and it would save me reattaching
each user database, recreating logins etc etc.

Or can I restore it and then use sp_dropserver, sp_addserver, bearing
in mind its clustered?
Thanks in advance

Barry

#3

There is no way. The only way to do it is uninstall and
reinstall your instances on a cluster. Once you do, you
can restore your client DBs, but any security things like
users with SIDs would be orphaned.

#4

I can tell you, there is no way other than uninstalling
and reinstalling that will do it correctly and properly.
Remember that just restoring master and such DOES NOT
change registry entries, etc. And on a cluster, the last
thing you want to do is hack around the registry.

Clusters, while in many ways similar to standalone, are
also very different. This is one of those cases. Having
done clustering for years and written quite extensively on
the topic, the story hasn't changed since I first touched
it.

#5

BarryLynch wrote:

Quote:

Hi All
Client has decided they want to rename the Virtual SQL Server from
(lets say) SQLA to SQLB.

To avoid to reinstall the server, could you set an alias on your DNS server?
In this way your client can connect to SQL Server with both SQLA or SQLB

Quote:

Thanks in advance

Barry

Bye

--
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org

#6

Alan
Forgive me for drawing this out but you seem to be strong in this area and
I'd like to get this out of my system and tease it out a bit - I take it
then that you think that the KB article is indeed wrong so we are in
improvisation territory. Here's the scenario in brief...

1. uninstall sql server
2. Evict all nodes (node names, IP Addresses, dsn servers etc remain the
same)
3. Create new cluster with new name and ip
4. Reinstall SQL Server with a new name for the VS with a new IP

This now contains a master database SQLB that is perfectly "synchronised" to
the new cluster

If theoretically we did a field by field compare between SQLA master and
SQLB master where would we find the differences relating to the Cluster

What is the relationship between SQLA master and the registry, can you point
to any particular keys?

Have you ever tried the drop_server, add_server approach? Anecdotally...I
had to do it a maybe 2 years ago on a 2-node when the owners had renamed the
server after they'd installed the cluster - this was breaking replication
because of the inconsistent @@server name value and they were not in a
position to uninstall (manufacturing plant). There were no problems with the
server although I concede the scenario is not the same. My point is that
conventional wisdom is uninstall but it was not necessary
in that case and I'm now trying to understand why a restore master won't
work in this one

I'm not disputing your expertise but I just don't understand where the
issues are

Actually when I have time I'm going to to this in our lab and report back on
my hacking

Regards

Barry Lynch

"Allan Hirt" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Quote:

I can tell you, there is no way other than uninstalling
and reinstalling that will do it correctly and properly.
Remember that just restoring master and such DOES NOT
change registry entries, etc. And on a cluster, the last
thing you want to do is hack around the registry.

Clusters, while in many ways similar to standalone, are
also very different. This is one of those cases. Having
done clustering for years and written quite extensively on
the topic, the story hasn't changed since I first touched
it.

#7

I don't know where it was assumed that we will not have to uninstall virtual SQL Server 2000 to rename the Virtual server name. Sure, it has to be uninstalled. That is the
only supported way and that is what is documented in

INF: How to Change a Clustered SQL Server Network Name
http://support.microsoft.com/?kbid=307336

Here it says clearly that " The proper way to rename a clustered SQL Server 2000 Virtual Server is to uninstall and reinstall SQL Server 2000 with the new Virtual Server
name."

You DO NOT have to evict the nodes ( you can if you want to but you don't have to do). I am referring to the steps in one of the previous post

" 1. uninstall sql server
2. Evict all nodes (node names, IP Addresses, dsn servers etc remain the
same)
3. Create new cluster with new name and ip
4. Reinstall SQL Server with a new name for the VS with a new IP".

--- In this steps 1 and 4 are required. Steps 2 and 3 are not. Why do we need to evict all nodes ? which basically means uninstall Windows Cluster and then reinstall it.
Not required at all.

-- After installing SQL Server with a new virtual name and IP, the qs is how do you get the dbs. You can make use of the dbs (system and user dbs) of SQL Server that
you uninstalled. If the paths are the same then YES we can replace the new mdf and ldf files with the old ones. I have done this many times on standlone SQL Servers
and few times on clustered SQL Server but not very recently. The only thing I believe we will need to do is run sp_dropserver and sp_addserver to have the new server
name. I will do some research to see if anything else is required and post the information.

-- Another option is to transfer the logins (a search will give you the KB) and then attach the user dbs.

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

#8

Let's be clear: to rename you have to uninstall the SQL
Server instance ONLY. That's what I've been saying all
along. You don't have to evict the nodes first; the SQL
Server uninstall process will remove all traces of SQL
Server except any data files you created.

Then you reinstall your virtual server with your new name.

You do not have to uncluster the nodes or re-confugure the
server cluster unless you want to rename that as well.

Keep in mind that you can still only have one default
instance; all others you install will need to be named
instances.

Quote:

-----Original Message-----
I don't know where it was assumed that we will not have
to uninstall virtual SQL Server 2000 to rename the Virtual

server name. Sure, it has to be uninstalled. That is the

Quote:

only supported way and that is what is documented in

INF: How to Change a Clustered SQL Server Network Name
http://support.microsoft.com/?kbid=307336

Here it says clearly that " The proper way to rename a
clustered SQL Server 2000 Virtual Server is to uninstall

and reinstall SQL Server 2000 with the new Virtual Server

Quote:

name."

You DO NOT have to evict the nodes ( you can if you want
to but you don't have to do). I am referring to the steps

in one of the previous post

Quote:

" 1. uninstall sql server
2. Evict all nodes (node names, IP Addresses, dsn servers
etc remain the
same)
3. Create new cluster with new name and ip
4. Reinstall SQL Server with a new name for the VS with a
new IP".

--- In this steps 1 and 4 are required. Steps 2 and 3 are
not. Why do we need to evict all nodes ? which basically

means uninstall Windows Cluster and then reinstall it.

Quote:

Not required at all.

-- After installing SQL Server with a new virtual name
and IP, the qs is how do you get the dbs. You can make use

of the dbs (system and user dbs) of SQL Server that

Quote:

you uninstalled. If the paths are the same then YES we
can replace the new mdf and ldf files with the old ones. I

have done this many times on standlone SQL Servers

Quote:

and few times on clustered SQL Server but not very
recently. The only thing I believe we will need to do is

run sp_dropserver and sp_addserver to have the new server

Quote:

name. I will do some research to see if anything else is
required and post the information.

-- Another option is to transfer the logins (a search
will give you the KB) and then attach the user dbs.

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and
confers no rights.

Are you secure? For information about the Strategic
Technology Protection Program and to order your FREE

Security Tool Kit, please visit

Quote:

http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet
access update their Microsoft software to better protect

against viruses and security vulnerabilities. The easiest

Quote:

way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

.

#9

Hi Uttam et al
I think we are more or less of agreement but I just need to clarify a
litle ona number of fronts

Front1: KBID 307336

1. Quote from KBID: 307336

"The proper way to rename a clustered SQL Server 2000 Virtual Server
is to uninstall and reinstall SQL Server 2000 with the new Virtual
Server name.

NOTE: Before uninstalling SQL Server 2000, make sure that you have
backed up the databases, including the master database. You can then
restore them after SQL Server has been reinstalled."

So the quote "you can then restore them" referring I take it to the
system databases including Master.

Objections
Conventional wisdom including a number of posts on this thread say
that restoring the master will not work because the cluster name and
or the SQL VS name has changed

Specific Question
Is the KB article correct?

Front 2. Evicting Nodes
I know I don't have to evict the nodes. The reason I put forward this
scenario is to form a framework for discussion of the issues of the
Registry and restoring the master - the pointof putting this in the
scenario was indeed as you say to effectively remove windows
clustering and reinstall so as to try and remove as many legacy
registry settings as spossible

Specific Question
What are these registry settings which effect the Master database?

Front 3. Sp_DropServer, Sp_AddServer
I aggree with you in that personally I think this would work and as I
mentioned in a previous post I have done it before on a cluster with
no ill effects
What I was hoping to achieve to with the initial posting in this
thread was to tease out any other issues

Specific Questions
Is dropserver, addserver enough to put SQLA master back in synch with
SQLB?
If not, what else is required

BTW I think this is an interesting thread and if I have offended with
any of my posts to date please forgive as its not intended - the devil
is in the detail no?

uttamkp (AT) online (DOT) microsoft.com (Uttam Parui[MS]) wrote in message news:<0bRCxkOdEHA.1828 (AT) cpmsftngxa10 (DOT) phx.gbl>...

Quote:

I don't know where it was assumed that we will not have to uninstall virtual SQL Server 2000 to rename the Virtual server name. Sure, it has to be uninstalled. That is the
only supported way and that is what is documented in

INF: How to Change a Clustered SQL Server Network Name
http://support.microsoft.com/?kbid=307336

Here it says clearly that " The proper way to rename a clustered SQL Server 2000 Virtual Server is to uninstall and reinstall SQL Server 2000 with the new Virtual Server
name."

You DO NOT have to evict the nodes ( you can if you want to but you don't have to do). I am referring to the steps in one of the previous post

" 1. uninstall sql server
2. Evict all nodes (node names, IP Addresses, dsn servers etc remain the
same)
3. Create new cluster with new name and ip
4. Reinstall SQL Server with a new name for the VS with a new IP".

--- In this steps 1 and 4 are required. Steps 2 and 3 are not. Why do we need to evict all nodes ? which basically means uninstall Windows Cluster and then reinstall it.
Not required at all.

-- After installing SQL Server with a new virtual name and IP, the qs is how do you get the dbs. You can make use of the dbs (system and user dbs) of SQL Server that
you uninstalled. If the paths are the same then YES we can replace the new mdf and ldf files with the old ones. I have done this many times on standlone SQL Servers
and few times on clustered SQL Server but not very recently. The only thing I believe we will need to do is run sp_dropserver and sp_addserver to have the new server
name. I will do some research to see if anything else is required and post the information.

-- Another option is to transfer the logins (a search will give you the KB) and then attach the user dbs.

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

#10

Sorry one other thing re KBID
If it is right but what is subsequently required is to dropserver,
addserver in order to resynch the server name then it sould be in the
KB article no?
After all just restoring the master with no further actions will cause
problems
so while it meets the requirements of it titles its note is not
complete

B

uttamkp (AT) online (DOT) microsoft.com (Uttam Parui[MS]) wrote in message news:<0bRCxkOdEHA.1828 (AT) cpmsftngxa10 (DOT) phx.gbl>...

Quote:

I don't know where it was assumed that we will not have to uninstall virtual SQL Server 2000 to rename the Virtual server name. Sure, it has to be uninstalled. That is the
only supported way and that is what is documented in

INF: How to Change a Clustered SQL Server Network Name
http://support.microsoft.com/?kbid=307336

Here it says clearly that " The proper way to rename a clustered SQL Server 2000 Virtual Server is to uninstall and reinstall SQL Server 2000 with the new Virtual Server
name."

You DO NOT have to evict the nodes ( you can if you want to but you don't have to do). I am referring to the steps in one of the previous post

" 1. uninstall sql server
2. Evict all nodes (node names, IP Addresses, dsn servers etc remain the
same)
3. Create new cluster with new name and ip
4. Reinstall SQL Server with a new name for the VS with a new IP".

--- In this steps 1 and 4 are required. Steps 2 and 3 are not. Why do we need to evict all nodes ? which basically means uninstall Windows Cluster and then reinstall it.
Not required at all.

-- After installing SQL Server with a new virtual name and IP, the qs is how do you get the dbs. You can make use of the dbs (system and user dbs) of SQL Server that
you uninstalled. If the paths are the same then YES we can replace the new mdf and ldf files with the old ones. I have done this many times on standlone SQL Servers
and few times on clustered SQL Server but not very recently. The only thing I believe we will need to do is run sp_dropserver and sp_addserver to have the new server
name. I will do some research to see if anything else is required and post the information.

-- Another option is to transfer the logins (a search will give you the KB) and then attach the user dbs.

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx