We have a sql server cluster in the corporate data center which normally provides the data services we need. Once in a while the various sites lose connectivity to the data center. One application which is in use at a satellite office and relies on sql server
must be available 24/7 and the loss of connectivity to the main sql server is always a big deal. We may want to install a server at the satellite office which replicates with the cluster; in the event that access to the sql cluster in corp is list, the users
would switch the client software over to pull data from the local sql server and continue with data entry. After connectivity is restored the changes would need to be replicated back to the corporate sql server.
It's a pretty low key application, max six users. It'd be nice if the main sql server and the standby local server were 100% in sync all the time, but if that's hard I don't think it'd matter to them if there was a small gap in the data. What kind
of sql server replication would be good for this scenario? I'm an application developer, not a sql dba, and I'm looking for some suggestions for solutions which may be available for SQL Server. It's currently running on sql server 2005, but we also have 2008
View Complete Post