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 |
|
JDMils
Starting Member
3 Posts |
 Posted - 2010-03-11 : 17:00:52
|
| I have a SQL 2005 Enterprise environment which I have inherited recently. The disk is 557 GB and the physical TempDB file is 499 GB!I have run the shrink commands as found on http://support.microsoft.com/default.aspx/kb/307487 without stopping the SQL services. I assume these steps have shrunk the virtual files within the TempDB.mdf only. I want to reduce the size of the MDF file so that it no longer uses 499 Gb of the data disk, but no matter what I do I can not find a solution which does not require a reboot of SQL services. Is this the only solution, to stop SQL services? If so, if I re-run the commands listed on the above MS article, will that shrink the physical file from 499 GB to a more reasonable size? Thanks.|+-- JDMils|+-- I know very little of SQL!!+-- SQL2005 ENT 64-Bit| |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-11 : 18:41:28
|
| It is a dangerous process if you don't stop SQL Services. Microsoft recommends that you run SQL Server in Single User Mode which, ipso facto, requires that you restart SQL Service (once to get it into single user, and again to get to back to multi user ...)Allowing any activity during the shrink of TEMPDB can have dire consequences. It just aint worth it!Just restarting the SQL Service should return TEMPDB to its original size, there should be no need to do anything else, but sometimes TEMPDB does not return to its configured startup size - in which case there are other steps you can take (easiest probably being to do the steps outlined in that article in single user mode) |
 |
|
|
|
|
|
TEMPDB filling up my HDD!?