This doesn't answer your question but I've always questioned the use of the Resource Governor on jobs. You know the jobs are there and you know they're going to be used. It would be better to tune the code so the jobs don't use so many resources but still get the job done. This also means that there's less likelihood of something going wrong because the jobs won't be running as long.
There might also be some jobs where using the Resource Governor causes them to not run in the night hours allotted to them.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs