Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Resource Governor Workload Classification limitations - looking for ideas Expand / Collapse
Author
Message
Posted Friday, August 02, 2013 3:45 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, April 09, 2014 12:26 PM
Points: 89, Visits: 318
Hi,

Many of our processes run as SQL jobs unfortunately. I would like to segment some groups of these off so that they are limited to resource pools but I am having some trouble seeing how to break them up with a classification function seeing as they all have the same host, user etc. Any ideas? Or maybe I am missing something or taking the wrong approach.

Thanks,
Scott
Post #1480635
Posted Friday, August 02, 2013 10:00 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 4:00 PM
Points: 35,967, Visits: 30,258
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.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

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."

"Change is inevitable. Change for the better is not." -- 04 August 2013
(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1480663
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse