Post reply

Tempdb Growth

  • December 17, 2019 at 3:21 pm

    #3708501

    Just be careful not to over-provision the number of files in TempDB.  The "standard" recommendation is 1 file per core up to 8 as a start and then tune from there.

    I'll also say that merely adding files when it seems necessary isn't necessarily the way to go.  If you have a lot of contention or even just a lot of large usage, then there's a huge probability that you have some code that is in desperate need of repair and you DO need to make such repairs.

    --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)
    Intro to Tally Tables and Functions

  • December 17, 2019 at 4:55 pm

    #3708531

    Thanks! One question, does "auto growth off" option is that a good practice for tempdb? Not sure if some will argue on this. In my case what i noticed is i have 2 sockets and 2 cpus and 2 tempdb mdf files and one log file, however the problem is only 10 GB totaldisk space is allocated to tempdb drive instead of 30 GB according to your theory and cause the disk space full? Please advise if i missing anything here?

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

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