Committed Trans Logs

hWe run full backup on our SQL2K databases everynight. After the backup, the
databases should truncate all committed transaction logs but trans logs are
not being truncating and it just grows and grows. I heard that poorly
written applications sometimes don't commited SQL trans logs propely after
the full backup thus creating a huge trans log files. Is there a way to
check whether trans logs are committed or not?
Thanks in advance.Daniel wrote:
> hWe run full backup on our SQL2K databases everynight. After the backup, the
> databases should truncate all committed transaction logs but trans logs are
> not being truncating and it just grows and grows. I heard that poorly
> written applications sometimes don't commited SQL trans logs propely after
> the full backup thus creating a huge trans log files. Is there a way to
> check whether trans logs are committed or not?
> Thanks in advance.
You're doing full backups, but you're not doing transaction log backups,
thus the committed transactions never get flushed from the log. Either
put the database into Simple recovery mode, or schedule transaction log
backups throughout the day. I have a script that you can use to
automate this:
http://realsqlguy.com/twiki/bin/view/RealSQLGuy/AutomaticBackupOfAllDatabases
Tracy McKibben
MCDBA
http://www.realsqlguy.com