FIX: A dump file is generated when you enable system-versioning on a table in SQL Server 2016

Applies to: SQL Server 2016 Service Pack 1SQL Server 2016 DeveloperSQL Server 2016 Enterprise

Symptoms


This issue occurs when you enable system-versioning on a table or a table that's supposed to become its history table, and the table is referenced by an indexed view in Microsoft SQL Server 2016. You may also receive the following error messages:
Msg 596, Level 21, State 1, Line LineNumber
Cannot continue the execution because the session is in the kill state.
Msg 0, Level 20, State 0, Line LineNumber
A severe error occurred on the current command.  The results, if any, should be discarded.


 

Resolution


This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 1 for SQL Server 2016 Service Pack 1 (SP1)

Cumulative Update 4 for SQL Server 2016



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.