A deadlock condition occurs when you make updates on a memory-optimized temporal table and you run the SWITCH PARTITION statement on a history table in SQL Server 2016

You run the SWITCH PARTITION statement on a disk-based history table of a memory-optimized system-versioned temporal table. If you run some In-Memory online transaction processing (OLTP) workloads that update the system-versioned temporal table in parallel, a deadlock condition may occur. Additionally, the process that is running the OLTP workloads is selected as the deadlock victim.
The fix for this issue is included in the following cumulative update for SQL Server:

About cumulative updates for SQL Server
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:

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.

Article ID: 3174712 - Last Review: 07/25/2016 22:26:00 - Revision: 1.0

Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Enterprise Core

  • kbqfe kbfix kbexpertiseinter kbsurveynew KB3174712