Symptoms
Assume that you have an in-memory online transaction processing (OLTP) database in Microsoft SQL Server 2014, and the database contains a memory optimized table with a nonclustered index. In this situation, database recovery may take longer than expected, and the CPU usage may approach 100 percent during the recovery process.
Note
-
Memory optimized tables with only hash indexes are not affected by this issue.
-
Recovery can occur when you start an instance of SQL Server, restore a backup or set a database online.
Resolution
The issue was first fixed in the following cumulative updates of SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
