Sentinel: The Transaction log is 99% full

  • 3427752
  • 02-Nov-2006
  • 26-Apr-2012


Microsoft Windows Server 2003 Standard Edition
Microsoft Windows 2000 Server
RedHat Linux
Solaris 9


The system events show, "the transaction log is 99% full, please resize." When running a big a report, it will fill the transaction log and the reports will not return data.


By default, in Sentinel 5.1.x with SQL 2000 server setup, the transaction log size is set to 2GB. There will be a constant need to increase the size if the logs are not backedup. Space in the transaction logs can not be reused until a transaction log backup is run which will clean up inactive transaction log entries and frees up transaction log space. So transaction log backups should be scheduled in SQL Server throughout the day (3 to 4 times a day depends on EPS) to free up space.

Reports (which is a select statement) should never use transaction log space . Only update transactions (like insert, update, delete) will use transaction logs space.