FIX: "Non-yielding Scheduler" occurs when you run queries with batch-mode hash join and/or sort in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you use Microsoft SQL Server 2016 or 2017. When you run some queries that use batch-mode hash join and/or batch-mode sort, you may notice these queries can spill a lot of data because of memory pressure, and a "Non-yielding Scheduler" condition occurs.


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


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:


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