(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
This wait type is just as the Books Online entry describes. You will see this wait type at most once per 823/824 error.
(Books Online description: “Occurs when the background suspect page logger is trying to avoid running more than every five seconds. Excessive suspect pages cause the logger to run frequently.”)
Questions/comments on this wait type? Click here to send Paul an email, especially if you have any information to add to this topic.
Added in SQL Server version:
Removed in SQL Server version:
Extended Events wait_type value:
The map_key value in sys.dm_xe_map_values is 231 in 2008 and 2008 R2, 238 in 2012, and 245 in 2014 RTM. After 2014 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.
I have not seen this wait type be a noticeable contention point, but if you’re seeing this wait type become prevalent, you are experiencing repeated 823/824 errors. This either indicates a large amount of corruption, or the workload is repeatedly hitting the same set of corrupt pages.
Known occurrences in SQL Server (list number matches call stack list):
- Waiting before checking the bad page list after processing the previous bad page
Abbreviated call stacks (list number matches known occurrences list):