A non-yielding scheulder is typically a token of a bug in SQL Server. Had you been on a fully supported version of SQL Server, I would have recommended you to open a case with CSS. But since you are on an old version, I can only recommend you to upgrade. SQL 2022 should be released before the end of the year, so that would be a good version to aim for.
sql server froze for few mins.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 54%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
Heisenberg
266
Reputation points
hi folks,
We are on following sql server
Microsoft SQL Server 2014 (SP3-CU4-GDR) (KB4583462) - 12.0.6433.1 (X64) Oct 31 2020 02:54:45 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)
its a 2 node always on cluster, synchronous , manual failover.
Today for 5 mins our SQL Server froze, all connections got disconnected and everyone was able to connect back after 5 mins.
Sp_Readerrorlog shows attached error. Any idea which way i can troubleshoot this issue?
SQL Server | Other
4 answers
Sort by: Most helpful
-
Erland Sommarskog 129.6K Reputation points MVP Volunteer Moderator2022-10-16T10:20:14.837+00:00 -
PandaPan-MSFT 1,931 Reputation points2022-10-17T01:26:31.3+00:00 Hi @Heisenberg ，
We can see that your system Idle is too much high, and your Interval is not very optimistic too, which is a very typical Non-yielding Scheduler error. To solve this error ( a bug), like Erland said upgrading is the best and easiest way.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"
-
Heisenberg 266 Reputation points
2022-10-17T15:52:22.927+00:00 @Erland Sommarskog i see below article that shows error similar to what i got, but its not applied to SQL 2014 and We are on SQL 2014
-
Erland Sommarskog 129.6K Reputation points MVP Volunteer Moderator
2022-10-17T20:19:24.807+00:00 "Non-yielding scheduler" is a quite common error due to the nature of the SQL Server OS. So the issue fixed in that KB article may or may not be one you ran into. Let's see, it was fixed in SQL 2019 SP4. This must have been in 2020. Which means that SQL 2014 was out of support. This means that even if they verified that the issue existed in SQL 2014, they did not fix it.
But, again, you have run into something else.
Tom's idea about VMware appears relevant. Because what's a little unusual in your case is that the issue resolved by itself. In many cases, you need to restart SQL Server when you have a non-yielding scheduler.
-
PandaPan-MSFT 1,931 Reputation points
2022-10-18T05:32:25.4+00:00 Hi @Heisenberg ,
Actually, I think the meaning of article is also to recommed you to upgrade your SQL. The 2014 version may have some other bugs you haven't came cross
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
Tom Phillips 17,781 Reputation points2022-10-17T19:26:03.7+00:00 Are you using VMWare?
If so, see:
https://kb.vmware.com/s/article/1002836