Currently we use terminalservers to enable remote users to work with a central LOB-application. The terminalserver is on the same LAN as the
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:
SQL over internetis 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)
Mirrorwill be removed in a future version of Microsoft SQL Server. Afak, it leaves the mirror constantly in restore-mode so the
LOB-applicationcan't actually use, correct?
Always On availability groupslook very complicated to me but they do support
Active Secondary Replicaswhich 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.