For databases utilizing Availability Groups. This wait is used internally while SQL Server is waiting to access the compressed log block cache. Log compression is an optimization used to decrease the number of messages sent to secondary replicas. As this is an optimization values are not necessarily problematic. If values are excessive further investigation is required

Resolved by


Suggested solutions

  1. Check the SQL Server error log for more information
  2. Examine wait statistics on the instance for other Availability Group issues. Investigate accordingly
  3. Rewrite modification DML that performs small (row-by-row) changes. Batch modifications result in less transaction log usage and messages across the network
  4. Remove unnecessary indexes, less messages and transaction log usage on modifications

Additional research

AlwaysOn Availability Groups Troubleshooting and Monitoring Guide

⇐ Back to index