July 30, 2008 at 10:10 am
posted it in wrong group.. but can't delete it.. sorry..
hi,
I have a log file that is 30GB big, every 15 min. I do a translog backup, with truncate, and the files are about 10 mb.
when I look at the proberties the initial size is about 30GB,
if I only have about 10 mb of transactions every 15 min. and they are truncated, why is the initial size so big? if ones the log has been 30 GB maybe because of faulty backup. does the initial size automaticlly grow to the largest know size!?
PS the DB is about 14GB and I'm running SQL 2005
if I do a DBCC SHRINKFILE, do I get a smaller initial size??
regards
Thomas
July 30, 2008 at 10:35 am
Use DBCC SHRINKDB command rather than DBCC SHRINKFILE command.
July 30, 2008 at 11:06 am
just founded out, it does.. growth to current size, so if it ones has reached ex. 30GB initial size will stay until I make a SHRINK_XX but was is the difference between SHRINKFILE / DB.. ? when it is done on the translog?
July 30, 2008 at 11:43 am
I would use SHRINKFILE specific to the log file.
Whenever I have something like that happen I usually execute the following:
use master
backup log DB_NAME with truncate_only
use DB_NAME
dbcc shrinkfile(LogFileName, 5000)
GO
5000 is just 5GB there.
MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
August 6, 2008 at 10:10 am
For tgh:
ShrinkDB shrinks a database.
Shrinkfile shrinks a specific database file. A database may have many files.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply