Occurs when a task is waiting to see whether log truncation frees up log space to enable the task to write a new log record. Consider increasing the size of the log file(s) for the affected database to reduce this wait. Information from Microsoft®
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.
LOGMGR_RESERVE_APPEND
Category: Log
SQL Server versions: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017
What is LOGMGR_RESERVE_APPEND?
1 Answer
|
|
answered 3348 days ago
Spotlight Essentials
|
|
|
This wait never occurs for most instances
For each of 4207 instances, we ranked LOGMGR_RESERVE_APPEND on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.
Prevalence of LOGMGR_RESERVE_APPEND across the Spotlight Population
For 92 % of hours with this wait, average wait time is around 990 ms
For each instance, we found all the recent hours when it had a LOGMGR_RESERVE_APPEND wait. We found the average latency for each of those hours.
34 instances contributed data to this chart