Hi All
I remember seeing a KB on the issue of renaming a server
name after SQL has been installed. It had something to do
with the fact that SQL binds itself to the server name. I
can't seem to find the article again. Any ideas or
thoughts?
Thanks
Jonolookup RENAMING SERVERS in BOL, you will have to do
sp_dropserver <old_name>
go
sp_addserver <new_name>
go
If you created any jobs under the old server name you will have to change
the originating server in sysjobs in the MSDB database, also, make sure your
service account has appropriate permissions to the new servername (like
ability to log on)HTH-- Ray Higdon MCSE, MCDBA, CCNA--"Jono"
<anonymous@.discussions.microsoft.com> wrote in message
news:2d06101c39438$59fc1d00$a601280a@.phx.gbl...
> Hi All
> I remember seeing a KB on the issue of renaming a server
> name after SQL has been installed. It had something to do
> with the fact that SQL binds itself to the server name. I
> can't seem to find the article again. Any ideas or
> thoughts?
> Thanks
> Jono|||Using
sp_dropserver <old_name>
go
sp_addserver <new_name>
go
doesn't seem to work for SQL7 and you have to run setup
again. The setup process will ask if you want to upgrade,
select yes and sql will assume the new name of the server.
Mark S
>--Original Message--
>lookup RENAMING SERVERS in BOL, you will have to do
>sp_dropserver <old_name>
>go
>sp_addserver <new_name>
>go
>If you created any jobs under the old server name you
will have to change
>the originating server in sysjobs in the MSDB database,
also, make sure your
>service account has appropriate permissions to the new
servername (like
>ability to log on)HTH-- Ray Higdon MCSE, MCDBA, CCNA--
"Jono"
><anonymous@.discussions.microsoft.com> wrote in message
>news:2d06101c39438$59fc1d00$a601280a@.phx.gbl...
>> Hi All
>> I remember seeing a KB on the issue of renaming a server
>> name after SQL has been installed. It had something to
do
>> with the fact that SQL binds itself to the server name.
I
>> can't seem to find the article again. Any ideas or
>> thoughts?
>> Thanks
>> Jono
>
>.
>
Showing posts with label remember. Show all posts
Showing posts with label remember. Show all posts
Friday, March 30, 2012
Wednesday, March 21, 2012
Rename A Server
We want to migrate a SQL 7 to SQL2000 (there will be a new box) and then rename the old SQL 7 box and keep it on the network.
Seems like I remember there is a problem when your rename a SQL server.
Anyone have experience with this?
Thanks
ChuckCheck this out (http://www.databasejournal.com/scripts/article.php/1496451)|||...And this is what M$ says about this process:
Q. Can I rename a server after installing SQL Server 2000?
A: Yes, you can rename a server after the installation of SQL Server 2000. When the SQL Server service starts for the first time after the name change, it automatically recognizes the change and resets the computer name. You do not need to run setup again to reset this value. However, you must perform several additional configuration steps. To correct the sysservers system table, you should manually run the following procedures.
For a default instance: sp_dropserver <old_servername>
go
sp_addserver <new_servername> , local
go
For a named instance:sp_dropserver <old_servername\instancename>
go
sp_addserver <new_servername\instancename> , local
go|||Thanks.
I'll try that. It is actually SQL 7. We are upgrading a SQL 7 server to SQL 2000. The SQL 2000 is a new box and we want to keep the SQL 7 server around on the lan for a while.
Thanks again
Chuck
Seems like I remember there is a problem when your rename a SQL server.
Anyone have experience with this?
Thanks
ChuckCheck this out (http://www.databasejournal.com/scripts/article.php/1496451)|||...And this is what M$ says about this process:
Q. Can I rename a server after installing SQL Server 2000?
A: Yes, you can rename a server after the installation of SQL Server 2000. When the SQL Server service starts for the first time after the name change, it automatically recognizes the change and resets the computer name. You do not need to run setup again to reset this value. However, you must perform several additional configuration steps. To correct the sysservers system table, you should manually run the following procedures.
For a default instance: sp_dropserver <old_servername>
go
sp_addserver <new_servername> , local
go
For a named instance:sp_dropserver <old_servername\instancename>
go
sp_addserver <new_servername\instancename> , local
go|||Thanks.
I'll try that. It is actually SQL 7. We are upgrading a SQL 7 server to SQL 2000. The SQL 2000 is a new box and we want to keep the SQL 7 server around on the lan for a while.
Thanks again
Chuck
Subscribe to:
Posts (Atom)