Re-size TempDB files

  • Comments posted to this topic are about the item Re-size TempDB files


  • Hi,

    remove *.ndf file is very delicate, cause for best performance with tempdb , you have to add a number of tempdb files equal to the number of processor's.

    regards ,

  • You have to be careful how you use the word RESTRICTED in SQL Server. Using the startup instance of

    C:\SQL\MSSQL.1\MSSQL\Binn>sqlservr.exe -c -f

    puts the instance in minimal configuration. This is for setting of a configuration value The option enables the sp_configure allow updates option. On the other hand, the term RESTRICTED in SQL Server refers to the USER that can access things such as the RESTRICTED_USER option of the ALTER DATABASE command. RESTRICTED here refers to only members of the db_owner fixed database role and dbcreator and sysadmin fixed server roles that can connect to the database. MINIMAL CONFIGURATION and the term RESTRICTED are two totally different things in SQL Server, where semantics does matter. Regards. Travis.

    "Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"

  • The -m parameter is definitely needed to prevent any other dbo or administrator type access - this is especially true during outages on production SQL servers.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • I had heard that you could

    • Stop the service
    • Kill the TempDB files
    • Start the service

    The downsides are two: (1) stopping the service, and (2) not being able to control where TempDB lives. This resets the Missing/Unused index statistics that SQL server keeps for you and that can be a bad thing as well.

    ATBCharles Kincaid

  • The article is right in time for me. I’ve just added new ndf files to TempDb. Unfortunately, there is a small issue that surprised me. As you can see in attached Word file, that result of run of EXEC sp_helpfile and SELECT * FROM sys.master_files is different for initial size and current file size of TempDb.

    Can anybody explain what does it mean and if there is a way to resolve it without service restart?

    It is working and there is no problem with that but if I run DBCC SHRINKDB, the initial size for Tempdb.mdf will jump to 6Gb and files will not be same size that may lead to disproportional load. I am not afraid to make each file 6Gb but the server doesn’t need 6*8=48Gb Tempdb.

    Initially TempDb had size of 6Gb and I had no problem adding ndf files with initial size of 500Mb. However, every attempt to reduce initial size of TempDB.mdf resulted in error message: “MODIFY FILE failed. Specified size is less than current size."

    My last step was: SSMS --> TempDB --> Properties --> Files --> Initial size modified to 500; Click OK; Restart Service. After that TempDB is 4Gb (8*0.5).

    Alex Prusakov

  • My experience was the same, if you use the gui - ssms it lets you reduce the size of the file. I created 4 x 4gb files and re sized them in the gui to 1 Gb each, with windows explorer open you could actually see the file size change - no service restart was needed. Although I would point out this was a new server build not being used in production at the time.


  • I have bad feelings if one table (sys.master_files) has one values and another (sys.database_files) is different. It would be great to know how to sink all.

    Alex Prusakov

  • Thank you for the article. The text looks very odd with all the HTML tags exposed when I view it (happens in both IE7 and FireFox3). Is it just me?

  • Looks like bunch of XML tags are getting exposed. I see them in the edit mode too. I took them out and resubmitted the article but I will also get in touch with the editor to see what's going on here.

    I hope the new submission shows clearly.


Viewing 10 posts - 1 through 9 (of 9 total)

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