From: Mike N. 

On Sun, 29 May 2005 18:02:12 -0700, Ellen K.  wrote:

>Hey, there's my hot failover then.   :)
>
>If I have a clone of a SQL Server box (matching boot partition and full
>transactional replication of the database) and the production one fails,
>we could just change the IP address of the clone and the users would
>never notice.   Or?

  This should basically work from a system standpoint.   I have never tried
this with SQL server so I don't know the SQL server implications such as
what it takes to get the replication target to serve as primary and how to
properly restore the primary.

   Users would likely notice during the period where someone notices that
the primary has crashed/failed and checks it out.   Everyone on the LAN
segment where the server is located would also need to clear their ARP
table to recognize the new server.  I think Windows will do this
automatically when the target host is unreachable, but a router such as
Cisco *may* retain the ARP table entry until timeout (hours?) even when the
target doesn't respond.

--- BBBS/NT v4.01 Flag-5