Occurs when databases inside an Availability Group states are synchronized. For example when a database receives a fail-over request the primary becomes synchronized and the secondaries shift into their preferred state (read-only, synchronizing, etc)

Resolved by


Suggested solutions

  1. Some values are expected, if values are excessively high investigate SQL Server error log

Additional research

AlwaysOn Availability Groups Troubleshooting and Monitoring Guide

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index