Applies ToSQL 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

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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.