FIX: Unexpected blocking or deadlocks after you install deprecated Cumulative Update 6 for SQL Server 2014 SP1
Assume that you install the original released and now deprecated Cumulative Update 6 for SQL Server 2014 Service Pack 1 (SP1) (build number 12.0.4449.0, KB 3144524), and that you are running workload patterns that include parallel SELECT(…)WITH NOLOCK, under the default SQL Server lock-based isolation level or a higher level. In this situation, you may encounter queries that experience blocking or deadlocks.
The patterns that are exposed to this blocking issue are as follows:
- Executing a parallelized SELECT (…) INTO Table FROM SourceTable statement, and specifically using the NOLOCK hint, under the default SQL Server lock-based isolation level or higher. In this scenario, other queries that try to access SourceTable will be blocked.
- While one transaction is holding an exclusive lock on an object (for example, an ongoing table update), another transaction is executing parallelized SELECT (…) FROM SourceTable by using the NOLOCK hint. In this scenario, the SELECT query that is trying to access SourceTable will be blocked.
This problem was first fixed 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: 3167394 - Last Review: 05/31/2016 15:41:00 - Revision: 2.0
Microsoft SQL Server 2014 Service Pack 1
- kbqfe kbfix kbsurveynew kbexpertiseadvanced KB3167394