Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Assume that you run a complex parallel query that requires a significant number of parallel threads in Microsoft SQL Server 2012 or in Microsoft SQL Server 2014, and the worker threads are exhausted on the corresponding scheduler. In a rare condition, the query does not make any progress for indefinite time because of undetected deadlock.

Note If other schedulers in SQL Server have available workers, the database engine will be able to process other queries correctly.


When starvation of worker threads occurs, a specific wait between worker threads is not treated as a potential blocker. Therefore, the deadlock monitor does not detect the condition. This causes the query to be not responding. The probability of such condition to occur is low, and mainly depends on the query plan shape, the degree of parallelism, and the worker threads availability.


Cumulative Update information

The issue was first fixed in the following cumulative update of 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. We recommend that you download and install 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.

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.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!