SQL Transaction Log Backup & Purge
The SQL transaction log maintains data from write and delete operations and is used to rollback transactions.
If the database model is set to FULL and not SIMPLE, this log file will continue to retain data until a transaction log backup is performed or the server runs out of space.
A large transaction log will affect database performance and can cause slowness or timeout issues. Performing a log backup will truncate data that is no longer needed.
It is recommended to backup the transaction log daily. This can be automated with SQL Agent for Standard and Enterprise editions of SQL Server. If you running SQL Express, you can change the database model to SIMPLE to automate the truncation process.
How to perform a transaction log backup
- Connect to the LobbyCentral database server using SQL Management Studio
- Create a folder on the database server to store the backup. i.e. c:\backup.
- Right click the lobbycentral database and choose Tasks, Backup.
- Take a full backup the database.
- Go back to Tasks, Backup
- Change the Backup Type to Transaction Log
- Set the Backup Destination to Disk and click Remove to remove the first backup's filename. For identification purposes, you should append the word log to the new filename as shown below.
- Click OK.
- After the backup finishes, you will need to reduce the physical size of the log file.
- Right-click the lobbycentral database and choose Properties
- Click the File page
- Locate the row for the Log and change the Initial Size to 100 or other preferred value.
- Optionally you may set the max size of the file in the column to the right of the Initial Size column.
- Click OK