How to duplicate the Non-Yielding scheduler case?

Question

I want to do some debugging practices for the Non-Yielding scheduler situation by windbg, so may I know is there any way to duplicate the issue?
Please click the Mark as Answer button if a post solves your problem!

Answer 1

I want to do some debugging practices for the Non-Yielding scheduler situation by windbg, so may I know is there any way to duplicate the issue?
Please click the Mark as Answer button if a post solves your problem!
Its very hard to duplicate the issue.See what causes the issue is when some poorly written query run from application and is such a complex one that it takes sceduler and does not gives it back.When query is submitted it is assigned thread to run and schedulers
run this thread.After query is completed this scheduler moves to run other thread  now if query is such that it keeps on running and does not finishes  your scheduler will be busy.So if you want to reproduce this issue (
Which could be dangerous and can lead to shutdown of SQL Server)
you need to submit a query which works in a way that it hogs scedulers.
I would advise to you not to run this on production( I guess you must be aware about this situation)
What you can also do is on this forum search for Non Yeilding schedulers and look for post where OP has posted Scheduler dump copy it to your environment and test it one such sceduler dump is in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/fbf1ad50-b9ae-4388-b03d-08374da85974/nonyielding-scheduler?forum=sqldatabaseengine
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
Thank you
Shanky.
I understand the theory for the Non-Yielding scheduler ,The reason I need to duplicate the issue in the test environment is just to study the debugging skills if I meet the Non-Yielding
scheduler situation later.
Please click the Mark as Answer button if a post solves your problem!