KB3210395 - 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 1 SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use) SQL Server 2016 Web - duplicate (do not use)

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:

Note

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

About the cumulative update

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update 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.