What is causing the Always On AG issue? Is it cluster, AD, DNS, or SQL?
AG (Always On Availability Groups) is a logical container that holds one or more user databases that failover together. So, if there is an issue with AG, where do you look? This blog post is an index map of the resources that are currently available and the ones to come. This post also provides pointers on which support topic to select if you choose to open a support case with CSS but why open a CSS case if you can quickly resolve the issue with minimal business impact based on the helpful resources included here?Ignite 2022: Announcing new features in Azure Database for MySQL – Flexible Server
Today, we're pleased to announce a set of new and exciting features in Azure Database for MySQL - Flexible Server that further improve the service's availability, performance, security, management, and developer experiences!
Troubleshooting data movement latency between synchronous-commit AlwaysOn Availability Groups
First published on MSDN on Apr 05, 2018 Writer: Simon SuTechnical Reviewer: Pam Lahoud, Sourabh Agarwal, Tejas ShahApplies to: SQL Server 2014 SP2, SQL Server 2016 SP1, SQL Server 2017 RTM In synchronous-commit mode AG nodes sometimes you may observe your transactions are pending on HADR_SYNC_COMMIT waits.
