When I have a SQL SERVER 2000 database in a Full Recovery model, I notice
the transaction log just keep getting bigger and bigger.
Will doing a Complete backup and backup the transcation log as part of the
maintenance plan truncate the transaction log ?
Thanks.

Truncate - yes.
Stop the growth - probably.
Make it smaller - no

Please read the information in BOL regarding the recovery model and how to
choose one that fits your needs.  It sounds like you haven't given
sufficient thought to this entire process - including how you use the
various backups to actually recover your system in the event of a loss or
failure.

Tlog backup will truncate the inactive part i.e. commited transactions of
the log file and minimize the log. Full backup do not shrink tlog.


Show quoteHide quote

fniles (fni***@pfmail.com) writes:
If you never back it up, that's the way it goes.

Yes, but as other have said, it will not shrink it. To shrink you need to
use DBCC SHRINKFILE, but you should only shrink if have been any exceptional
event, as for instance not having backed up the transaction log for the
last six months. If you back up the log regularly, the log will grow to
the size it needs, and you should let it stay that way.

Hello,

If it is FULL recovery; please schedule a FULL database backup once a day
and schedule the transaction log backup every 30 minutes or so...
This will help you to recover the database and keep the LDF file grown in
control.


Thanks
Hari

Show quoteHide quote

Backup using the proxy account in SQL2005
BCP genric error
Problem on scripting stored procedures
Telling if SQL2005 is running
SMSS - script to new window uses sp_executesql?!