Diagnose Unexpected Failover or Availability Group in RESOLVING State
First published on MSDN on Nov 26, 2014 AlwaysOn availability groups use Windows Cluster to 1) detect the health of the SQL Server process that hosts the primary replica, and 2) to fail over the availability group resource, if configured to do so.Making Service Broker Application Highly Available With AlwaysOn
First published on MSDN on Jan 26, 2017 If you have a Service Broker (SSB) application connecting to SQL Server using an AlwaysOn availability group listener, in the event of an unexpected failover, some messages may be lost or stuck in the transmission queue on the old primary (new secondary) after the failover.Improved AlwaysOn Availability Group Lease Timeout Diagnostics
First published on MSDN on Feb 23, 2016 When your AlwaysOn availability group is configured for automatic failover, you may find your availability group failed over, or if configured for manual failover, you may observe your availability group transition from the PRIMARY role to the RESOLVING role, during which users cannot access the availability group databases.
