There is a base, some labels are created as memory optimized, I included this base in always on as usual, but the data diverges - on the secondary replica in the table, the data is on the transaction back. Here it says https://blogs.msdn.microsoft.com/arvindsh/2014/09/24/potential-data-latency-with-alwayson-availability-groups-and-memory-optimized-tables/ that a few seconds delay is possible , but much more has passed, and the data diverge. What is the problem? How to achieve data consistency?
- You apparently somehow did not very carefully read the information on the link given by you. The person writes just that even after a few seconds of waiting, the data did not appear on the secondary, and how he solved it, and gives a link to the documentation, where it is explained, and gives the recommended way to solve the problem . optimized table on the primary replica " . In version 2016, this moment seems to be fixed. - i-one
|