SQL Server 2016 SP2 installation : Configuring TEMP DB Initial Size and Autogrowth

  • Hi, Currently our databases are in SQL Server 2008 R2 and we are upgrading to SQL Server 2016.
    I wanted to know how shall I determine the Temp initial size ? By default it gives me 4 files and initial size 8 MB . We have a separate drive for TEMPDB which is 100 GB
    Shall I give total initial size (data + log file )  almost equal to 100 GB ?
    does this look correct : total number of files=4 ( we have 4 logical processors) , initial size =16000 , total size = 16000*4=64000 MB
    tempdblog = initial  size=30,000

    Currently in SQL Server 2008 R2 the Temp DB is configured as :
    tempDEV             initial size            8 MB      Autogrowth by 10%, unrestricted
    tempLOG             initial size           1 MB     Autogrowth by 10%, unrestricted

    Thanks,
    Janki

  • SJanki - Wednesday, June 27, 2018 2:41 PM

    Hi, Currently our databases are in SQL Server 2008 R2 and we are upgrading to SQL Server 2016.
    I wanted to know how shall I determine the Temp initial size ? By default it gives me 4 files and initial size 8 MB . We have a separate drive for TEMPDB which is 100 GB
    Shall I give total initial size (data + log file )  almost equal to 100 GB ?
    does this look correct : total number of files=4 ( we have 4 logical processors) , initial size =16000 , total size = 16000*4=64000 MB
    tempdblog = initial  size=30,000

    Currently in SQL Server 2008 R2 the Temp DB is configured as :
    tempDEV             initial size            8 MB      Autogrowth by 10%, unrestricted
    tempLOG             initial size           1 MB     Autogrowth by 10%, unrestricted

    Thanks,
    Janki

    No one can really tell you the initial size as we have no idea how tempdb is used on that instance. People can guess but that's all it is - a WAG. You can probably guess better by looking at the current systems tempdb as that should give you some idea of the space needed.
    If you are going to use autogrowth, don't set it to a percentage but rather a fixed size. It used to be that one eighth the size of the file was recommended but I haven't seen that for awhile. Probably because it depends. If you know the current growth rate or have some projections from the current system, that would give you a better idea of what to use.

    Sue

  • Sue_H - Wednesday, June 27, 2018 3:04 PM

    No one can really tell you the initial size as we have no idea how tempdb is used on that instance. People can guess but that's all it is - a WAG. You can probably guess better by looking at the current systems tempdb as that should give you some idea of the space needed.
    If you are going to use autogrowth, don't set it to a percentage but rather a fixed size. It used to be that one eighth the size of the file was recommended but I haven't seen that for awhile. Probably because it depends. If you know the current growth rate or have some projections from the current system, that would give you a better idea of what to use.

    Sue

    Thank you Sue. This is helpful !

  • This was removed by the editor as SPAM

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

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