June 26, 2002 at 8:35 am
I've got a SQL Server 2000 database (about 80 MB) under normal load, and in spite of a maintenance plan that backs up the transaction log, the log still grows to 5-8 GB over a two week period. I have most of the useful admins scripts posted on this site (many thanks), but I need a clue about how to manage transaction log size in a "normal" way. Should SQL Server be controlling the size of the transaction log (per the maintenance plan), or do transaction logs require constant attention?
June 26, 2002 at 9:24 am
Are you backing up the database? What recovery model are you set to (database/properties)?
Normally a database backup truncates the log, allowing space to be reused.
Steve Jones
June 26, 2002 at 10:17 am
The recovery model is FULL.
June 26, 2002 at 12:41 pm
are you backing up the database?
Can you give the schedule?
Have you tried dbcc shrinkfile? I know that isn't the best solution, but you could easily schedule this if you have issues.
Also, how big are the transaction log dumps? Are they growing as well?
Steve Jones
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply