Waitopedia is a comprehensive resource of information about SQL Server waits.

The description shown below is the top answer as voted by the Spotlight community.

The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.


Category: Idle
SQL Server versions: 2012, 2014, 2016, 2017

This is an idle wait and so it can be safely ignored.


2 Answers


Waiting for log records to become available. Can occur either when waiting for new log records to be generated by connections or for I/O completion when reading log not in the cache. This is an expected wait if the log scan is caught up to the end of log or is reading from disk. Information from Microsoft®


I have about 30 % of this wait on one instance

Very rare

This wait never occurs for most instances

For each of 4207 instances, we ranked HADR_LOGCAPTURE_WAIT on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of HADR_LOGCAPTURE_WAIT across the Spotlight Population

For 23 % of hours with this wait, average wait time is less than 240 ms

For each instance, we found all the recent hours when it had a HADR_LOGCAPTURE_WAIT wait. We found the average latency for each of those hours.

110 instances contributed data to this chart

Latency Distribution of HADR_LOGCAPTURE_WAIT across the Spotlight Population