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

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


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:


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.