Post reply

tempdb space issues

  • October 29, 2019 at 12:08 am

    #3692566

    MVDBA (Mike Vessey) wrote:

    Its ALWAYS the dba's fault - we just get used to it 🙂

    Heh... not me... and they know better than to try... especially if they want help with the problem. [/quote]

    MVDBA (Mike Vessey) wrote:

    ..as for code … the number of times I've heard "can't you just throw some more hardware at it" … I die a little each time

    I've learned to play the game there.  The last time I heard that type of dribble, I kept my mouth shut.  I knew extra hardware wouldn't help (in fact, I sent an email to people that had no control over any of it that stated that it would actually make it worse to add memory and CPUs... and it did... increased rollbacks by a whopping 30%) but I thought it an excellent opportunity to 1) make the point that they always griped about but we had no physical proof in the past and 2) I'll never turn down hardware.

    You can usually only get away with something like that once per company but I've been there long enough for such a proof to be forgotten and so I've gotten two awesome upgrades that I'd have otherwise had to beg for. 🙂

    --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 post 16 (of 16 total)

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