|
Home > Archive > MS SQL Server > October 2006 > Change in Server Name for SQL Server 2000
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Change in Server Name for SQL Server 2000
|
|
| sasiraj 2006-10-24, 6:29 pm |
| Hi,
I am having a SQL Server 2000 EE SP3 with default instance .
This Server's name need to be changed.
Could any tell me whether there needs to be any configuration done on
the
SQL Server prior to the change. and also after the name change.
Thanks in Advance!!
| |
|
| Renaming a SQL server is no big effort.
Simply run the following SQL once you have renamed the server against the
master database.
sp_dropserver OLDSERVERNAME
go
sp_addserver NEWSERVERNAME, local
go
If you have any remote logins or replication setup, you may experience an
error dropping the server. If you do, you will need to drop the remote
logins first.
You will know this by running the above SQL either way. If it works, you're
done.
If not - look up "issues with remote logins and replication" in BOL.
Immy
"sasiraj" <vardhansasi@gmail.com> wrote in message
news:1158655746.621017.22620@i42g2000cwa.googlegroups.com...
> Hi,
>
> I am having a SQL Server 2000 EE SP3 with default instance .
> This Server's name need to be changed.
>
> Could any tell me whether there needs to be any configuration done on
> the
> SQL Server prior to the change. and also after the name change.
>
> Thanks in Advance!!
>
| |
| Tibor Karaszi 2006-10-24, 6:29 pm |
| .... and some additional thoughts here: http://www.karaszi.com/SQLServer/ i...n
ame.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
"Immy" < therealasianbabe@hot
mail.com> wrote in message news:OoAeN$82GHA.4932@TK2MSFTNGP02.phx.gbl...
> Renaming a SQL server is no big effort.
>
> Simply run the following SQL once you have renamed the server against the master database.
>
> sp_dropserver OLDSERVERNAME
> go
> sp_addserver NEWSERVERNAME, local
> go
>
> If you have any remote logins or replication setup, you may experience an error dropping the
> server. If you do, you will need to drop the remote logins first.
> You will know this by running the above SQL either way. If it works, you're done.
>
> If not - look up "issues with remote logins and replication" in BOL.
>
> Immy
> "sasiraj" <vardhansasi@gmail.com> wrote in message
> news:1158655746.621017.22620@i42g2000cwa.googlegroups.com...
>
>
|
|
|
|
|