FIX: Potential loss of historical data when you alter an in-memory temporal table in SQL Server 2016
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: Recommendation: Install the latest cumulative update for 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:
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.
Article ID: 3178137 - Last Review: 07/25/2016 22:09:00 - Revision: 1.0
Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Enterprise Core
- kbqfe kbfix kbexpertiseadvanced kbsurveynew KB3178137