FIX: "Non-yielding" error occurs when there is a heavy use of prepared statements in SQL Server 2014, 2016 and 2017

Applies to: Microsoft SQL Server 2014 Service Pack 2SQL Server 2014 DeveloperSQL Server 2014 Enterprise


Assume that you use an application to connect to an instance of Microsoft SQL Server 2014, 2016 and 2017. If there is an intensive use of the sp_prepare stored procedure (SP) that is not immediately followed by sp_unprepare, many SQL handle cached entries are generated. Additionally, a non-yielding scheduler error may appear in the error log.


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.