(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 in a parallel scan needs access to the parent dataset, generally to get the next range of rows to scan.
(Books Online description: “Used to synchronize child dataset access to the parent dataset during parallel operations.”)
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 DATASET_PARENT map_value in sys.dm_xe_map_values.
The map_key value in sys.dm_xe_map_values is 7 in 2008 and 2008 R2, and 1 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.
Although this latch can be a contention point, it’s only applicable to parallel scans, and so the parallelism itself is what should be investigated. See the CXPACKET wait type for information on investigating and addressing unwanted or skewed parallelism.
Also 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):
- Getting the next range to scan from the parent dataset (in this case, while scanning a heap as part of a nested-loop join)
- Setting up the scan for a child thread (in this case, while scanning an index as part of a sort operation)
And many, many more similar stacks around parallel scans.
Abbreviated call stacks (list number matches known occurrences list):