Friday, February 24, 2012

How to correct registry in renamed server

If a log shipping server must take on the name of another server during
failover, the name in the server registry will not be the same as the name of
the server. What is the best way to correct this?
--
Regards,
JamieFound it
SQL Server 2000
sp_dropserver 'old server name'
sp_addserver 'new server name', 'local'
Delete the entry in Enterprise Manager for the old server name and then
youâ're golden. You will have to stop and start the SQL Server service to
complete the process.
--
Regards,
Jamie
"thejamie" wrote:
> If a log shipping server must take on the name of another server during
> failover, the name in the server registry will not be the same as the name of
> the server. What is the best way to correct this?
> --
> Regards,
> Jamie|||And if you are on 2000, you need to handle the Agent jobs as well:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:DFACE678-CD17-4B17-9E15-D5FDC74A0A2C@.microsoft.com...
> Found it
> SQL Server 2000
> sp_dropserver 'old server name'
> sp_addserver 'new server name', 'local'
> Delete the entry in Enterprise Manager for the old server name and then
> youâ're golden. You will have to stop and start the SQL Server service to
> complete the process.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>> If a log shipping server must take on the name of another server during
>> failover, the name in the server registry will not be the same as the name of
>> the server. What is the best way to correct this?
>> --
>> Regards,
>> Jamie

No comments:

Post a Comment