(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 latch class is when a thread is waiting for access to the DBCC MultiObjectScanner data structure that DBCC consistency checks use to drive scanning through the database. In this case, the latch controls the access necessary to load the MultiObjectScanner with the allocation units from one or more objects (multiple objects can be checked simultaneously). The various scanning threads inside DBCC then acquire the DBCC_MULTIOBJECT_SCANNER latch to request the next page (or range of pages) to scan for consistency problems. You can read more about this architecture in this blog post.
(Books Online description: “Internal use only.”)
Questions/comments on this latch class? 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 latch_class value:
Maps to the DBCC_CHECK_TABLES_INIT map_value in sys.dm_xe_map_values.
The map_key value in sys.dm_xe_map_values is 44 in 2008 and 2008 R2, and 38 in 2012 and 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 latch be a noticeable contention point.
See the LATCH_EX wait type for more information about latches in general and how to troubleshoot them.
Known occurrences in SQL Server (list number matches call stack list):
- Adding more allocation units into the DBCC MultiObjectScanner
Abbreviated call stacks (list number matches known occurrences list):