Consider the following scenario:
You're usign Microsoft SQL Server 2016.
You have a temporal table that's partitioned before or while turning on system versioning.
An automatically created (anonymous or default) history table is configured.
You turn off system versioning, and then you run an ALTER TABLE SWITCH PARTITION statement on the history table.
In this scenario, you receive an assertion error that resembles the following:
Msg 3624, Level 20, State 1, LineNumber
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.
Msg 596, Level 21, State 1, LineNumber
Cannot continue the execution because the session is in the kill state.
Msg 0, Level 20, State 0, LineNumber
A severe error occurred on the current command. The results, if any, should be discarded.
The fix for this problem is included in the following updates:
Each new build for SQL Server 2016 contains all the hotfixes and all the security fixes that were included with the previous build. We recommend that you install the latest build for SQL Server 2016.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.