September 5, 2003 at 10:18 am
hi,
last week the transaction log file of one of the databases grew from 30G to 60 G, is there a way to determine what made the log file grow.
September 5, 2003 at 10:47 am
Look at the log file and the log space consumption chart if data were gathered. There must be some poorly managed transactions...
September 5, 2003 at 11:39 am
Log Explorer from Lumigent could read back the log and you could see the transactions, but there could be a lot to go through.
Steve Jones
September 5, 2003 at 12:04 pm
quote:
last week the transaction log file of one of the databases grew from 30G to 60 G
Do you perform log backup regilarly? If you haven't done that, You should start it now.
Anything involves data changes (insert/delete/update), schema changes and reindex etc will be logged in transaction log file. You may check any large batch update/data import, reindexes and database maintenance tasks since last week.
September 6, 2003 at 5:28 am
This might help
http://www.support.microsoft.com/?id=317375
Ray Higdon MCSE, MCDBA, CCNA
------------
Ray Higdon MCSE, MCDBA, CCNA
September 7, 2003 at 5:12 am
What is the size of the database and is a log file size of 30Gb normal?
September 7, 2003 at 11:23 am
the size of the db is 1.2 TB and log file size is currently at 60GB
September 7, 2003 at 7:16 pm
September 7, 2003 at 8:01 pm
September 8, 2003 at 6:28 am
Use truncate the log on checkpoints, this will keep a check on the Log's file growth. Use TruncateLogOnCheckpoint, for more info check BOL or recommended sites.
September 12, 2003 at 4:18 pm
TruncateLogOnCheckpoint will disable point of failure recovery, you will have to rely on your last full backup.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply