The database transaction log file (e.g., ACCTivate$Demo_Log.mdf) may not get cleared until a full database backup is performed. This issue may be caused by not performing regular backups within Acctivate. Running a scheduled backup job from SQL Server Enterprise Manager may not be “truncating” the transaction log file.
You should shrink the transaction log file to fix this problem. Perform an Acctivate database backup using the Backup Company function within Acctivate or the Acctivate Database Maintenance tool if you cannot open Acctivate. You may be required to free up enough disk space for the backup file before you start.
Related Microsoft KB Articles:
- How to stop the transaction log of a SQL Server database from growing unexpectedly
- Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE