Select the product you need help with
FIX: "Process <block list> appears to be non-yielding on Scheduler <ID>" error message when you run a query in SQL Server 2012Article ID: 2762557 - View products that this article applies to. On This PageMicrosoft distributes Microsoft SQL Server 2012 fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2012 update release. SymptomsConsider the following scenario:
Process <block list> appears to be non-yielding on Scheduler <ID> CauseThis issue occurs because the sort operator traverses many buckets in an internal SQL Server list of memory allocations to find the next available memory from the buffer pool. When the server has a large memory, the internal SQL Server list of memory allocations in the buffer pool grows to a large size also. Therefore, the sort operator traverses many buckets in the internal SQL Server list of memory allocations to find the next available memory from the buffer pool. This behavior does not yield on the scheduler frequently enough. Therefore, the "non-yielding scheduler" error is reported frequently. ResolutionCumulative update informationCumulative update package 1 for SQL Server 2012 Service Pack 1The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2765331 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2765331/
)
Cumulative update package 1 for SQL Server 2012 Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was releasedSQL Server 2012The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:2758687 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2758687/
)
Cumulative update package 4 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Properties | Article Translations
 |
Back to the top
