|
Home > Archive > MS SQL Server > February 2006 > Renaming warm standby server to assume role of primary.
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 |
Renaming warm standby server to assume role of primary.
|
|
|
|
I've been shipping logs to a warm standby server and now wish to switch to
this server in order to perform maintenance on the primary server. (Both are
running SQL Server 2000 Standard Edition). I intend to take the primary
server offline, and rename the standby server so all clients on the domain
will point to it.
I vaguely remember reading somewhere that after renaming a server, the SQL
service may not start due to a checksum failure and that reinstall may be
necessary. However, I haven't been able to find any more details on the
matter. Since alot of work went into creating a fully synchronized copy of
the server instance, I want to avoid a reinstall at all costs.
Other articles out there make no mention of such a potential problem. Does
anyone have information they can share on this issue? Thanks.
| |
| Tibor Karaszi 2006-02-04, 8:23 pm |
| The "server not start" issue was on 7.0. Here are some thoughts no server rename:
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/
Blog: http:// solidqualitylearning
.com/blogs/tibor/
"vic" <vic@discussions.microsoft.com> wrote in message
news:DEB352ED-4596-48C0-9DA8- 2CB208F1FBBD@microso
ft.com...
>
> I've been shipping logs to a warm standby server and now wish to switch to
> this server in order to perform maintenance on the primary server. (Both are
> running SQL Server 2000 Standard Edition). I intend to take the primary
> server offline, and rename the standby server so all clients on the domain
> will point to it.
> I vaguely remember reading somewhere that after renaming a server, the SQL
> service may not start due to a checksum failure and that reinstall may be
> necessary. However, I haven't been able to find any more details on the
> matter. Since alot of work went into creating a fully synchronized copy of
> the server instance, I want to avoid a reinstall at all costs.
> Other articles out there make no mention of such a potential problem. Does
> anyone have information they can share on this issue? Thanks.
| |
|
|
|
|
|