Manage SQL transaction logs
- Last UpdatedDec 13, 2022
- 1 minute read
The transaction log is a stream of records that records every change to the database from the point the database was created until the current point in time. Every logged operation creates a log record. The log records generated by a transaction are written to disk when the transaction commits.
Due to the large number of record changes, transaction logs can become large very quickly. This can impact SQL Server performance and AVEVA™ Production Management performance, and can result in running out of disk space.
Options for managing transaction logs
There are two options for managing transaction logs:
-
Implement a backup strategy that truncates the transaction log on a regular basis.
-
Verify that databases are configured to use simple recovery model. AVEVA™ Production Management is designed to use the simple recovery model by default on the configuration database.
Transaction log file size could still become an issue on the data repository. The data repository typically has the full recovery model as default. You will need to put a backup plan in place for the data repository, including truncation of the transaction log.