If we are to reduce Consistency to Eventual Consistency (maybe, whenever), there are far better choices amongst the NOSQL (as in Not Only SQL) out there. Then it comes down to what "neat feature" suits best for your implementation.
Microsoft announced general availability of its Azure Data Sync tool this week, which allows data to be synchronised between cloudy Azure SQL databases and on-premises servers. Just in time for Azure to go for a good long lie down, in Northern Europe at least. Microsoft Azure on show at Ignite in Orlando Microsoft Azure …
Wednesday 20th June 2018 21:20 GMT FozzyBear
By pointing applications at their local copy of the database, Microsoft reckons that access time and responsiveness will be improved significantly and latency and connection failures reduced.
So, Microsoft, what you are saying, is that cloud based solutions are a crappy alternative to managing your data on your own network. Good to know. Thanks
Thursday 21st June 2018 00:37 GMT Claptrap314
"SQL Server greybeards"? Hardly in this case. We had a MySQL server doing almost this exact thing in 2008. Our farm was in various Texas cities when I started, most states when my turn came in the buy out & shut down cycle. The difference? No troubles replicating all types of data for MySQL.
(In 2009, I wrote code to use federated views to constrain which columns we exported. I learned all about those triggers.)