This post has been republished via RSS; it originally appeared at: SQL Server Support articles.
First published on MSDN on Sep 08, 2018I wrote an article to discuss about data movement latency between AG groups:
https://blogs.msdn.microsoft.com/psssql/2018/04/05/troubleshooting-data-movement-latency-between-synchronous-commit-always-on-availability-groups/
Now I develop a tool to analyze AG log block movement latency between replicas and create report accordingly (this tool has been updated to Version 2.0).
You can download it here: https://github.com/suyouquan/AGLatency/releases/download/v2.2/AGLatencyV2.2.zip
Video:https://github.com/suyouquan/AGLatency/blob/master/AGLatency_HowTo.mp4
User Manual: https://github.com/suyouquan/AGLatency/blob/master/AGLatencyTool_UserManual_V2.pdf
You capture log block Xevent trace from both primary and secondary replica for 5-10 minutes and then this tool will generate report about the latency of the log block movement.
Regards,
Simon