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.

  • This was removed by the editor as SPAM

  • It's been a while since I have dealt with log shipping, but when we were using it, we decided that it would be easier to reconfigure the application to point at the standby rather than rename the server.

    /*****************

    If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek

    *****************/

  • In the interest of closing the thread, I found what I needed at Tibor's Karaszi's site: http://www.karaszi.com/SQLServer/info_change_server_name.asp .

    Thank you both for following up. 

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply