- 01 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Transactions Log file keeps growing.
- Updated on 01 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Problem:
SQL Transactions Log file keeps growing.
Cause:
When SQL runs a backup, the Transaction Log is truncated. SQL Agent never ran, Transaction Log size kept growing.
Solution:
To free up the space in the SQL Server transaction log for the Pharos Database, follow these steps:
Close all connections to the Pharos Database on SQL Server by stopping the Pharos Database Service and any dependant Pharos Print Services. Also close any copies of Pharos Reports that may be running.
Open SQL Query Analyzer, logging on as 'sa' or a user with System Administrator rights and run following SQL query:
sp_detach_db 'pharos'
Open Windows Explorer and browse to the location where the SQL Server data files are located, e.g. c:\MSSQL7\Data. There should be two files related to pharos database (pharos_data.mdf and pharos_log.ldf). Delete the old log file that is now too big (pharos_log.ldf). You may need to delete the file from Recycle Bin as well.
Switch back to SQL Query Analyzer and run the following SQL query:
sp_attach_single_file_db @dbname ='pharos', @physname = 'c:\MSSQL7\Data\pharos_data.mdf'
Restart the Pharos Services (starting with Pharos Database Service).