Last Post 30 May 2002 12:03 PM by augustinius. 0 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
augustinius
New Member
New Member

--
30 May 2002 12:03 PM
Wish it were that simple, but it really is not always. We had tempdb grow to over 1 GB once (because of the log entirely), and simply using DBCC ShrinkDB or ShrinkFile would not work, because you can't "truncate" the log of TempDB. There was nothing in the system to shrink the file, and we needed the space (test rig with limited budget, unfortunately). So what we had to do was this: ALTER DATABASE MODIFY FILE where we re-pointed TempDB's log file to a different file with a different size value. Then we had to stop and restart the service (be VERY careful, because if SQL Server can't create the file, because of permissions, lack of a directory, etc., SQL Server will not start). SQL Server created the new log file and we could safely delete the old file.

You are not authorized to post a reply.

Acceptable Use Policy