Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
loiter99
Starting Member
38 Posts |
 Posted - 2006-05-19 : 08:52:06
|
| Hello, I have read through all the tempdb posts and couldn't find one that matched my situation.Windows 2003Sql Server 2000 Sp4TempDb grows every night to 20 gigs, leaving less than 1 gig on the drive during the day. The database has most of that space free, so I am not worried about crashing during the day.I have run shrinkfile in the past and it has worked, today I ran it on tempdev and while I get no error, the datafile doens't shrink (log file is not an issue).So, my question is why won't it shrink? I know this is potentially dangerous from pervious posts, but this is a production server and I can't reboot until the evening.ThanksJeff |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-05-19 : 09:05:22
|
| Why are you shrinking the file? It grows to 20GB during the day, you shrink it and then the server has to reallocate it (probably 1MB at a time if its set to the default) until its back up to 20GB the next day, probably with excessive fragmentation in the process - I reckon you'd be better off to leave it alone!Note also that if any activity happens on TEMPDB whilst you are shrinking it then TEMPDB will most likely become corrupted, therefore MS advises that you should only shrink TEMPDB whilst SQL Server is running in single user mode:http://support.microsoft.com/default.aspx/kb/307487Kristen |
 |
|
|
|
|
|
Temp DB size