Transaction log for database [...] is full Error
When running RTA you get an error that, The transaction log for database '...' is full, for the RTA database. This error is more likely to happen when running a Special Utility Routine / Rebuild Utility in RTA, as those routines generate significantly more data transactions.
No matter what operation you are doing in RTA, your database log file is out of room for one of 3 reasons:
- Your log is set to autogrow, but can't because your SQL Server has insufficient disk space to grow the log.
- Your log is not set to autogrow, you are running in Full recovery mode, and you have not performed a transaction log backup recently.
- Your log is not set to autogrow, you are running in Simple or Bulk Logged recovery mode, and the log file isn't big enough to handle the amount of transactions between log commits.
First, identify what your log growth setting is set to. If set to auto-grow, first check to make sure you have sufficient disk space. If disk space isn't available, perform necessary actions to clean up old files and free up disk space.
Next, you should check to make sure that your log is being properly maintained.
Check your database recovery model.
If your recovery model is set to full, make sure that you have regularly scheduled log backups taking place. RTA recommends performing a full backup at least once per day, and a log backup at least twice per day. More frequent log backups may be necessary depending on your aversion to data loss or the availability of disk space on the server.
If your recovery model is set to simple, no log backups are required, and no further troubleshooting is required.
Follow the steps below to verify the database is set to "auto-grow", otherwise check to make sure you have sufficient disk space.