FIX: Potential loss of historical data when you alter an in-memory temporal table in SQL Server 2016

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


Assume that you perform an ALTER operation (schema modification or turning system-versioning off) on an in-memory temporal table. In this situation, you may lose some of the historical data that is stored in an internal history table at the moment of query execution.

During that operation, about one million rows will be moved from internal to an on-disk history table.


The issue was first fixed in the following cumulative update of SQL Server:


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


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