Rename SQL Server 2005 Virtual Server

Hi everybody,
I'm having a big problem when I want to rename my Failover Clustered SQL
Server 2005 Virtual Server. I've followed the indications given in this
how-to: http://msdn2.microsoft.com/en-us/library/ms178083.aspx but when I
try to bring my SQL Server online (after changing the network name, of
course...) I get this error:
[sqsrvres] GetRegKeyAccessMask: Could not get registry access mask for
registry key Software\Microsoft\Microsoft SQL Server\MSSQL.3\Cluster (status
0))
If I return back to the Virtual Server's old name I can bring SQL Server
online allright...
I've found no information about this error. Can anybody help me?
Thanks in advance,
Petrus
Create the following regkey:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsof t SQL Server\MSSQL.3\Cluster]
"ClusterName"="<NewVirtualServerName>"
I had the same problem, and MSSQL.3 referred to Reporting Services. I'm guessing that since Reporting Services isn't cluster aware, the parameters aren't updated (or even created). But when SQL starts all its instances up, it gets confused that the parameter isn't there to change.
However, this still didn't have the desired result for me. The database engine and the OLAP services were MSSQL.4 and .5 respectively. The cooresponding Cluster keys as above continually renamed themselves back to the old name.
-Tom Kretzmer
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||Sorry to post an update so soon. Just update MSSQL.4 and .5 on both nodes of the cluster and restart resources. For some reason "select @.@.servername" still comes up as the old instance name, but everything else works as it should.
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Rename a SQL2005 Istance

I've installed a SQL2005 with named instance: SERVER\SQL2005
Because some software does'nt recognize this instance, i'd like to rename it
to default instance.
Is it possibile ?
How ?
Mauro
Mauro Miotello wrote:
> I've installed a SQL2005 with named instance: SERVER\SQL2005
> Because some software does'nt recognize this instance, i'd like to rename it
> to default instance.
> Is it possibile ?
> How ?
> Mauro
>
You'll have to uninstall the named instance and the run the install
again. In the new install you can install it as a default instance.
Regards
Steen
|||"Steen Persson (DK)" <spe@.REMOVEdatea.dk> ha scritto nel messaggio
news:eNXySxTSGHA.4440@.TK2MSFTNGP11.phx.gbl...
> You'll have to uninstall the named instance and the run the install again.
> In the new install you can install it as a default instance.

Removing SQL Instance Name

Hi,
I've MS SQL MSDE 2000 in my m/c. I've the server as an instance. I
want to have the server without any instance name. I want to keep all
the databases and data as it is. How can i remove the instance name?
ie. from "servername\vsdotnet" to "servername" alone.
Thanks,
Senthil.
- copy off the mdf and ldf files to a safe location
- uninstall the named instance
- install the default instance
- copy back the mdf and ldf files and attach them
Vikram
Vikram Vamshi
Eclipsys Corporation
"Senthil" <kumar.senthil@.gmail.com> wrote in message
news:4dce1b6a.0406201015.7891a725@.posting.google.c om...
> Hi,
> I've MS SQL MSDE 2000 in my m/c. I've the server as an instance. I
> want to have the server without any instance name. I want to keep all
> the databases and data as it is. How can i remove the instance name?
> ie. from "servername\vsdotnet" to "servername" alone.
> Thanks,
> Senthil.
|||Hi,
Only way is to backup the dabases, Remove the existing instance and install
a default instance and Restore the backed files.
Other option is detach databases , Remove existing named instance, Install
default and Attach the
Steps:-
1. Start SQL Server in single user mode
2. Perform a backup (BACKUP database) of all databases. COpy the .BAK files
to safe loaction.
3. After this for safe pupose use SP_DETACH to Detach the databases
4. Copy the MDF and LDF files to a safe place
5. Remove named instance using COntrol panel -- add remove programs
6. Install SQL Server default instance and apply the same service pack as
old
7. Restore the Master database after starting the SQL Server in single user
mode.
8. After the Master database restore restore the other databases one by one.
Have a look into the below links for more information on moving datases with
various methods:-
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Note:
Please ensure that you take a backup and keep it in a safe place before
removing the named instance.
Thanks
Hari
MCDBA
"Senthil" <kumar.senthil@.gmail.com> wrote in message
news:4dce1b6a.0406201015.7891a725@.posting.google.c om...
> Hi,
> I've MS SQL MSDE 2000 in my m/c. I've the server as an instance. I
> want to have the server without any instance name. I want to keep all
> the databases and data as it is. How can i remove the instance name?
> ie. from "servername\vsdotnet" to "servername" alone.
> Thanks,
> Senthil.
|||Thanks a lot Vikram and Hari for your replies and links.
Regards,
Senthil.
"Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message news:<#YETuLyVEHA.3428@.TK2MSFTNGP12.phx.gbl>...
> - copy off the mdf and ldf files to a safe location
> - uninstall the named instance
> - install the default instance
> - copy back the mdf and ldf files and attach them
> Vikram
> --
> Vikram Vamshi
> Eclipsys Corporation

Removing Nodes from a Virtual Server?

I've build a SQL 2000 SP3a cluster on top of an 8 node Windows 2003 cluster.
We've decided to split the cluster up into 2 individual clusters and as such
I'm attempting to remove some of the cluster nodes from the Virtual Server
Definiton (as per the "Adding or Removing a Cluster Node from the Vritual
Server Definition" of
http://www.microsoft.com/technet/pro...clus.mspx#EGAA)
Anyway, I begin the SQL install and get to the Computer Name dialog where I
choose the virtual server name. I click next and the install GUI just
disapears. I check and setupsql.exe is continues to show up as running in
Taskman for about 10 minutes then just finishes up.
Any thoughts?
Anyone have any thoughts on this?
"Chris B." wrote:

> I've build a SQL 2000 SP3a cluster on top of an 8 node Windows 2003 cluster.
> We've decided to split the cluster up into 2 individual clusters and as such
> I'm attempting to remove some of the cluster nodes from the Virtual Server
> Definiton (as per the "Adding or Removing a Cluster Node from the Vritual
> Server Definition" of
> http://www.microsoft.com/technet/pro...clus.mspx#EGAA)
> Anyway, I begin the SQL install and get to the Computer Name dialog where I
> choose the virtual server name. I click next and the install GUI just
> disapears. I check and setupsql.exe is continues to show up as running in
> Taskman for about 10 minutes then just finishes up.
> Any thoughts?
|||Hi
Only 4 Nodes are supported on a cluster by SQL Server 2000. It is a setup UI
limitation.
You need to remove the installation like you installed it, with command
line.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:981588B6-717B-45C2-BBBA-F5C30A2AE5F2@.microsoft.com...[vbcol=seagreen]
> Anyone have any thoughts on this?
> "Chris B." wrote:
|||Hmm, thanks for the quick reply.
I don't believe I installed from a command line, but those few weeks were
pretty crazy Can you point me in the general direction of documentation
on the command line syntax? I assume you're talking about using the
sqlrem.bat file?
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Only 4 Nodes are supported on a cluster by SQL Server 2000. It is a setup UI
> limitation.
> You need to remove the installation like you installed it, with command
> line.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:981588B6-717B-45C2-BBBA-F5C30A2AE5F2@.microsoft.com...
>
>
|||I have not seen any. It was in a discussion with a developer from the SQL
Server Development Team.
PSS might be able to help.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:22265BEA-AD19-4C06-BFE6-146D419CCE10@.microsoft.com...[vbcol=seagreen]
> Hmm, thanks for the quick reply.
> I don't believe I installed from a command line, but those few weeks were
> pretty crazy Can you point me in the general direction of
> documentation
> on the command line syntax? I assume you're talking about using the
> sqlrem.bat file?
> "Mike Epprecht (SQL MVP)" wrote:

Removing AD from server with SQL on it

I've got a situation where I need to move a server (server A) from the
domain (Domain A) that it is in (it is the only server in this domain)
into a different domain (Domain B). The curve ball is that SQL 2005
is set up on this server.
My question is: How 'broken' will SQL become if I uninstall AD/remove
it from the domain that it is in? I've done some VMWare testing and
forcing the demotion on the SQL box and bringing it into the other
domain isn't that big of a deal. The SQL data that resides on the
server A is just test data but is close to being a production server.
A carbon copy of all the users in Domain B have been recreated on
Server/Domain A.
Comments/suggestions?
Thanks in advance...
I don't think, it matters much as long as the server name is the same. The
SQL instances running on the server should be able to function without major
issues.
You have to make sure the service logins, if using domain accounts, should
be changed to match the accounts in the new domain. Any windows logins that
are mapped to any database users should be modified as well. If you have
special processes like backups to shared drives or log shipping, you'll have
to make sure the folder are shared with appropriate permissions for the new
accounts.
Anith