Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 12119927
KB4338773 - FIX: Deadlock errors when you run an SSIS package in parallel in SQL Server - Microsoft Support
Last update date:
6/2/2022
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2017 Developer on Windows
SQL Server 2017 Enterprise on Windows
SQL Server 2017 Enterprise Core on Windows
SQL Server 2017 Standard on Windows
Affected releases:
build lower than 14.0.3223.3
Fixed releases:
14.0.3223.3
Description:
Symptoms
Assume that you use Microsoft SQL Server Integration Services (SSIS). When you run the SSIS package in parallel, you may experience deadlock errors.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 16 for SQL Server 2017 Cumulative Update 2 for SQL Server 2016 Service Pack 2
About Cumulative Update 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: Latest cumulative update for SQL Server 2017 the latest build for SQL Server 2016
Workaround
To work around this problem, change the SET TRANSACTION ISOLATION LEVEL SERIALIZABLE statement to SET TRANSACTION ISOLATION LEVEL REPEATABLE READ.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
SET TRANSACTION ISOLATION LEVEL (Transact-SQL) Learn about the terminology Microsoft uses to describe software updates.
