• Robert Davis (2/28/2013)


    ScottPletcher (2/28/2013)


    I have additional space to grow, you prevent it.

    So if a task unexpectedly needs, say, 50MB more of tempdb space to complete, you abend it -- perhaps after it ran for hours, so you can look forward to twice that long in rollback time -- while I let it complete.

    Umm, no. My file size is already much larger than yours, so if a process needs say 50MB more space, yours has to stall and perform an auto-grow while my continues onward happily because my file is already large enough.

    If on the other hand, the file has already autogrown to fill the entire drive (and mine is already pre-sized to that size) then where are you getting this additional space to grow like you say above? Please educate me on these magical tempdb drive fairies that give you additional space even when the drive is full.

    So you massively overallocate tempdb. That's one approach I guess, if you're not required to justify drive costs.

    Why do you insist on having all tempdb files on one drive? Given how proportional fill works, aren't you banging the bejeebers out of that one drive?

    SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.