February 24, 2006 at 7:30 am
My tempdb is located on my 10GB C:. For the past couple weeks the transaction log has been growing up to 4.5GB in size at which point the C: is full. I've tried:
use tempdb
dbcc shrinkfile (templog,0)
backup log tempdb WITH NO_LOG
dbcc shrinkfile (tempdev,0)
but that just tells me that the tempdb log is in use and cannot be backed up.
So what I would like to know is #1, is there a way to shrink the log file without having to restart SQL server and #2, is there an easy way to determine why the log file is growing so quickly. BTW, the recovery model is set to simple on tempdb.
February 24, 2006 at 11:44 am
Check this link
http://support.microsoft.com/default.aspx/kb/307487
Kindest Regards,
Sameer Raval [Sql Server DBA]
Geico Insurance
RavalSameer@hotmail.com
February 24, 2006 at 12:11 pm
All three of the methods described in that article require restarting the SQLServer service. I want to know a way to do this without having to restart it.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply