Re: replication and failover
I haven't done this myself but putting in an SQL proxy might be good enough.
Ur apps point to the proxy which "decides" which SQL server is the master
and routes transactions there. Meanwhile the slave is getting repl. updates
from the master so it too is up to date. If the master site gets blown up u
just set ur slave to master and flip (ur location neutral) proxy to the old
slave which is now the master.
REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=--
"...ne cede malis"