- Cumulative Update 2 for SQL Server 2016
- Cumulative Update 5 for SQL Server 2012 Service Pack 3 (SP3)
- Cumulative Update 7 for SQL Server 2014 SP1
If these HoBTs are later deallocated, the freed HoBT goes back to a global cache for reuse. When that HOBT is reused, it reuses the previously promoted latch, even when there is no contention on the HoBT. This adds CPU overhead. This behavior increases the privileged (kernel) mode CPU usage of SQL Server until the server is restarted. This increase typically adds no more than several microseconds with each execution. You may also see a high volume of PAGELATCH_* waits because of these extended super-latches on HoBTs.
Article ID: 3162589 - Last Review: Oct 5, 2016 - Revision: 1