FIX: SQL jobs fail due to blocking in SSISDB in SQL Server 2014 and 2016

S’applique à : SQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 Enterprise Core

Symptoms


Assume that you deploy a simple SQL Server Integration Service (SSIS) package into the SSIS Catalog (SSISDB). SSISDB needs to be run in parallel through various SQL jobs. You may notice that some SQL jobs fail due to blocking in SSISDB.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

Resolution


This issue is fixed in the following cumulative updates 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:

Workaround


To work around the issue, you can manually modify theStored Procedure [catalog].[set_execution_property_overrides] to set thetransaction level to repeatable read instead of serializable as follows:

Replace:

SET TRANSACTIONISOLATION LEVEL SERIALIZABLE

With:

SET TRANSACTIONISOLATION LEVEL REPEATABLE READ

References


Learn about the terminology that Microsoft uses to describe software updates.