Post reply

Resource Governor Workload Classification limitations - looking for ideas

  • August 2, 2013 at 3:45 pm

    #297164

    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

  • August 2, 2013 at 10:00 pm

    #1638394

    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.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply