A new Flexera Community experience is coming on November 18th, click here for more information.
Hello
We found out that the transaction log in FlexNetManager on Prem 2019R2 is very large, almost 1 TB. What can we do to minimize this? (See the Atachment).
Thnaks for your alway Professional Answers.
Thank You very Much from Switzerland (FHNW Higher Education Team SAM)
‎May 08, 2020 08:44 AM
One cause of a transaction log growing massively large would be that the transaction log is not being backed up on a regular basis. The transaction log in a SQL Server database (when configured in "Full" recovery mode) will grow indefinitely if it is never backed up. So perhaps verify the last time the log as backed up. After backing up the log, you will likely need to shrink the log file if you want to free up the disk space.
‎May 10, 2020 10:16 PM
You also have the option of setting the database recovery mode to "Simple" rather then "Full" which will reduce the size of the LOG file.
‎May 12, 2020 07:37 AM
One cause of a transaction log growing massively large would be that the transaction log is not being backed up on a regular basis. The transaction log in a SQL Server database (when configured in "Full" recovery mode) will grow indefinitely if it is never backed up. So perhaps verify the last time the log as backed up. After backing up the log, you will likely need to shrink the log file if you want to free up the disk space.
‎May 10, 2020 10:16 PM
You also have the option of setting the database recovery mode to "Simple" rather then "Full" which will reduce the size of the LOG file.
‎May 12, 2020 07:37 AM
Thank you both for the quick replies. The transaction log backup helped. Now the Tansaction log no longer grows.
‎May 13, 2020 04:02 AM
‎May 13, 2020 04:04 AM
User | Count |
---|---|
8 | |
6 | |
3 | |
3 |