Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 11455814
KB4057280 - FIX: High CPU use when large index is used in a query on a memory-optimized table in SQL Server - Microsoft Support
Last update date:
6/21/2022
Affected products:
SQL Server 2016 Service Pack 1
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2017 Developer
SQL Server 2017 Enterprise
SQL Server 2017 Enterprise Core
SQL Server 2014 Developer - duplicate (do not use)
SQL Server 2014 Enterprise - duplicate (do not use)
SQL Server 2014 Enterprise Core - duplicate (do not use)
SQL Server 2014 Standard - duplicate (do not use)
Affected releases:
build lower than 14.0.3022.28
Fixed releases:
14.0.3022.28
Description:
Symptoms
Consider the following scenario: You use in-memory Online Transaction Processing (OLTP) in Microsoft SQL Server 2017, 2016, and 2014. You execute a query on a memory-optimized table that contains a large index. In this scenario, if you use the large index during the query execution, the CPU use might sharply rise to 100 percent very quickly. If you have more than one logical processors, only one of the processors usage might rise to 100 percent quickly.
Cause
This problem occurs because the garbage collection in in-memory OLTP might take a long time to finish if a large index is used in a query execution.
Resolution
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 4 for SQL Server 2017 Cumulative Update 7 for SQL Server 2016 SP1 Cumulative Update 2 for SQL Server 2014 SP3 Note After you install this update, you must enable trace flag (TF) 9945 to fix this problem. To enable TF 9945, see the Trace Flags (Transact-SQL) topic on the Microsoft Developer Network (MSDN).
