Post reply

Splitting the tempDB, when is it too much?

  • January 29, 2009 at 10:17 am

    #128280

    So everything I've read says it's best practice to have your tempDB on it's own disks and to have an equal number of files as CPUs or CPU*Cores. Is there a limit to how many you should have? I was asked to set up SQL on a server with 8 quad core CPUs. Should I really have 32 tempDB data files? That seems like overkill to me.

    Thanks,

    Tim

  • January 29, 2009 at 2:02 pm

    #935062

    all depends on the amount of traffic you are getting...the big thing is its not going to hurt it!! it will allow the SQL OS to be a little more dynamic...

  • January 29, 2009 at 2:12 pm

    #935069

    Generally, I start with 1/2 or 1/4 the number of cores, and see if there's any contention on the allocation pages in Tempdb (which is the reason for splitting). If there is, split more. If not, leave the files as-is.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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