Growing Database Files

Question

Growing Database Files

Steve Jones - SSC Editor

SSC Guru

Points: 736172
More actions
March 2, 2016 at 10:11 pm

#311858

Comments posted to this topic are about the item Growing Database Files
March 2, 2016 at 10:55 pm

This was removed by the editor as SPAM

Viewing 14 posts - 1 through 13 (of 13 total)

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

Igor Micev SSC-Dedicated Points: 33109 More actions · Answer 1

This is practical when you add files to databases. Instead of calculating the number in KBs you just add MB or GB and task is done.

Thanks

Igor Micev,My blog: www.igormicev.com

Umer Akram SSC-Insane Points: 22209 More actions · Answer 2

thanks for the question Steve. that a very handy feature.

Ed Wagner SSC Guru Points: 287026 More actions · Answer 3

I must admit that I was looking for the trick and was curious when I couldn't find it. Thanks, Steve.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Hugh.lacey 1173 Valued Member Points: 65 More actions · Answer 4

Hugh.lacey 1173

Valued Member

Points: 65

March 3, 2016 at 6:36 am

#1862721

So is the file called tempdata or tempdev?

george sibbald SSC Guru Points: 104210 More actions · Answer 5

Hugh.lacey 1173 (3/3/2016)
So is the file called tempdata or tempdev?

tempdev

---------------------------------------------------------------------

Steve Jones - SSC Editor SSC Guru Points: 736172 More actions · Answer 6

tempdev is the logical name in the file. The physical name is tempdb.mdf

daniel.plocinik Hall of Fame Points: 3288 More actions · Answer 7

I am new to this gig so pardon my ignorance. One rule for using size is that it must be larger than the size you wish to change. Since the minimum size of databases prior to SQL Server 2012 was 2 MB how can the first two choices be correct? Am I missing something obvious?

Steve Jones - SSC Editor SSC Guru Points: 736172 More actions · Answer 8

All of those are valid statements in my SQL 2012 and SQL 2014 instances. Didn't try 2016, but I'm sure it's the same.

You have different control of tempdb. I believe the restriction on size is for user databases, not tempdb. There is this KB article that shows you can do this, and you will need to restart.

https://support.microsoft.com/en-us/kb/307487

Since tempdb is rebuilt on restart, I think the size applies then.

daniel.plocinik Hall of Fame Points: 3288 More actions · Answer 9

daniel.plocinik

Hall of Fame

Points: 3288

March 3, 2016 at 2:38 pm

#1862935

Thank you for the clarification Steve.

akljfhnlaflkj SSC Guru Points: 76202 More actions · Answer 10

akljfhnlaflkj

SSC Guru

Points: 76202

March 10, 2016 at 4:37 pm

#1864453

Thanks for the question.

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 11

Easy one, thanks.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

patricklambin SSCrazy Eights Points: 9994 More actions · Answer 12

Thanks for this interesting question. I knew the answer for the 2008 version ( up to 2014 ). For 2000 I used in only in 2003/2004 , for 2005 I never tried to shrink a data file and I am not sure that the TB was available . With 2008 , I had a Developer edition with which I have done many tests including this one . For the next versions , I have studied mainly the documentation to discover the differences with older versions.

Anyway , this discussion was interesting as it permits me to refresh my knowledge. So thanks for all the posters.