Symptoms

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.

Resolution

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

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 2017

Latest cumulative update for SQL Server 2016

More Information

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

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 terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×