FIX: SQL Server may generate EXCEPTION_ACCESS_VIOLATION dump file when you merge two partitions of system-versioned temporal tables in SQL Server 2016 or 2017

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


Consider the following scenario:

  • You use temporal tables in Microsoft SQL Server 2016 or 2017.
  • You partition both the current table that contains data and the history table.
  • You try to swap the oldest partition and split the earliest partition to create a new partition.

In this scenario, when you merge the oldest partition, you may receive the following error message. Additionally, an EXCEPTION_ACCESS_VIOLATION memory dump file is generated.

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.


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

       Cumulative Update 14 for SQL Server 2017

       Cumulative Update 4 for SQL Server 2016 SP2

       Cumulative Update 10 for SQL Server 2016 SP1

More Information

To get more information on partitioning with temporal tables, see Partitioning with Temporal Tables.


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.