Re-size TempDB files

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Amar Pogaku » Re-size TempDB files

Re-size TempDB files

Rate Topic

Display Mode

Topic Options

Author

Message

AmarPo

Posted Friday, April 03, 2009 12:37 AM

SSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 3:56 PM
Points: 38, Visits: 196

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

Amar

Post #689608

ESL_HSBC

Posted Friday, April 03, 2009 5:05 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, September 24, 2012 6:15 AM
Points: 8, Visits: 148

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 ,
eric.simbozel@hsbc.fr

Post #689731

TravisDBA

Posted Friday, April 03, 2009 5:10 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, May 09, 2013 9:23 AM
Points: 1,288, Visits: 2,996

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. ... BigGrin

Post #689733

rudy - Doctor "X"

Posted Friday, April 03, 2009 8:43 AM

Hall of Fame

Group: General Forum Members
Last Login: Yesterday @ 2:11 PM
Points: 3,108, Visits: 2,114

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.

Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."

Post #689975

Charles Kincaid

Posted Friday, April 03, 2009 10:54 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 9:18 AM
Points: 772, Visits: 1,825

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.

ATB

Charles Kincaid

Post #690089

Alex Prusakov

Posted Friday, April 03, 2009 11:29 AM

SSC Journeyman

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 8:55 AM
Points: 92, Visits: 192

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

Post Attachments

USE tempdb.docx (11 views, 215.69 KB)

Post #690099

iain27

Posted Saturday, April 04, 2009 9:47 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 8:39 AM
Points: 121, Visits: 314

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.

Iain

Post #690544

Alex Prusakov

Posted Sunday, April 05, 2009 12:30 PM

SSC Journeyman

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 8:55 AM
Points: 92, Visits: 192

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

Post #690642

mishaluba

Posted Sunday, April 05, 2009 4:34 PM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 5:54 PM
Points: 525, Visits: 617

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?

Post #690667

AmarPo

Posted Monday, April 06, 2009 1:28 AM

SSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 3:56 PM
Points: 38, Visits: 196

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.

Amar

Post #690777

« Prev Topic | Next Topic »

Permissions