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.
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.
This problem is fixed in the following cumulative updates for SQL Server:
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).
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: