FIX: SQL Server 2016 hangs when you restore databases that contain memory-optimized tables

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


When you restore a database that contains memory-optimized tables in SQL Server 2016, the server stops responding (hangs).

Cause


When a large volume of work is performed on memory-optimized tables in a single transaction (including LOBs), a checkpoint that's run immediately after that transaction takes longer than expected to complete. This issue also occurs during restore for redo of the same transaction.

Resolution


This update is included in Service Pack 1 for SQL Server 2016.

Note When this update is installed, the issue is resolved by increasing the size of an internal hash table tracking the LOBs to minimize the collisions.

Cumulative update information

The fix for this issue is included in the following cumulative update for SQL Server:

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology  that Microsoft uses to describe software updates.