FIX: Poor table scan performance when a query filters non-Primary Key columns on in-memory history tables

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

Symptoms


Assume that a user uses system-versioned temporal tables in SQL Server 2016. They use a query that filters non-Primary Key columns on in-memory history tables. In this case, poor performance occurs, and it takes a long time to complete the table scan.

Cause


This issue occurs because users cannot define indexes on in-memory history tables.

Resolution


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


Note After you install this update, you must set trace flag 10316 to enable the fix. To set trace flag 10316, see the Trace Flags (Transact-SQL) topic on the Microsoft Developer Network (MSDN) website.

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 Microsoft uses to describe software updates.