Best practice bring MS SQL database to remote sites

by roberth   Last Updated July 08, 2017 19:06 PM

Currently we use terminalservers to enable remote users to work with a central LOB-application. The terminalserver is on the same LAN as the MS SQL-server.

Now my question is: what is the preferred way to replicate/mirror the database to the remote sites, so users don't need a terminalserver and can work in their local LAN.

These are my concerns:

  1. SQL over internet is often too slow. It would however be my preferred solution because of simplicity (if internet doesn't work this will only temporary effect clients, no worry about shipping log files, etc)
  2. Mirror will be removed in a future version of Microsoft SQL Server. Afak, it leaves the mirror constantly in restore-mode so the LOB-application can't actually use, correct?
  3. Always On availability groups look very complicated to me but they do support Active Secondary Replicas which sounds like the ability that every remote site can use it's local replica for reading and the central-db for writing. However, I wonder, does this work with all LOB-applications? And does this require a very fast and stable internet-connection? It must not fail with every short internet/VPN hick-up.

Any recommendations? Or is a central terminal-server the only way?

Thanks in advance.



Related Questions


Distributed availability group not working with FCI

Updated November 07, 2017 12:06 PM


Moving from FCI to DAG

Updated October 19, 2017 14:06 PM