SYMPTOMS
Cluster Administrator provides a method to rename cluster
resources. To do this, right-click the resource in Cluster Administrator, and
then click
Rename.
However, renaming the SQL Server virtual, or clustered, servers is not supported in the current version of Microsoft SQL
Server. If you rename the SQL Server Network Name resource, a variety of
problems may occur. One of the problems that may occur is that the SQL Server virtual
server instance may no longer come online. When this problem
occurs, the following information may be logged in the application event log:
MSSQLSERVER Error (3) 17052 N/A BOPDEV1
[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message
= [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
MSSQLSERVER Error (3) 17052 N/A
BOPDEV1 [sqsrvres] ODBC sqldriverconnect failed
RESOLUTION
The correct way to rename a clustered SQL Server 2000 virtual server is
to remove and then reinstall SQL Server 2000 by using the new virtual server name.
This behavior is by design.
Note Before you remove SQL Server 2000, make sure that you have backed
up the databases, including the
master database. You can then restore the
databases after you reinstall SQL Server.
You can also rename your existing root
database folder \Data to a name that is similar to \DataSave. This folder is typically in the following location:
%Drive%\Program Files\Microsoft SQL Server\MSSQL\Data
To validate
the location, follow these steps:
- Start SQL Server Enterprise Manager.
- Right-click the instance of SQL Server that you want to remove, and then click Properties.
- Click the General tab.
- Click Startup Parameters.
The base data location is listed with the -d entry (example:
-dC:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf)
In addition to renaming your \Data directory, you can make
a separate copy of this folder and paste it in another location on the drive.
For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base:
224071
Moving SQL Server databases to a new location with Detach/Attach