How to reduce and limit the SQL transaction log file for ARM

• Sometimes the space on the SQL Server where the database files are stored is limited.

We recommend that you only perform this task when all ARM users are disconnected from the system.

Besides the following steps, please refer also to:

• https://documentation.solarwinds.com/en/Success_Center/ARM/Content/sql-server-database-maintenance.htm
• https://documentation.solarwinds.com/en/Success_Center/ARM/Content/configure-storage-of-scans-settings.htm
• https://documentation.solarwinds.com/en/Success_Center/ARM/Content/sql-express-and-arm.htm

1. Start and log in to the ARM configuration application.
2. Click on the Basic Configuration category.
3. Click the re-check icon in the lower right corner. A confirmation message "Configuration successfully loaded!" is displayed when re-check is complete.
4. In the SQL server section in the upper right corner you can see the currently used recovery mode and the buttons for the database maintenance:
   1. Switch between simple and full recovery mode
   2. Shrink the database log files
   3. Shrink the database
5. Select the second option "Shrink database logs". The setting is applied immediately.
6. (Optional) Set the retention period of stored scans in the database to a shorter interval.
   1. On the homepage of the ARM configuration application click Server.
   2. Under Storage of scans, specify the period of time for which the scans remain in the database.

• Limiting the size of the Transaction log file:
• The transaction log file when in simple mode, will reuse the space in the file when released, but it won't shrink by itself. For demanding transactions, the log file may grow extensively. You can set a limit for the Transaction log file in SSMS using the rule of thumb to be 20-30% of the Database file size and check if everything works fine. Depending on the size of the environment and of the Logga configurations, you may need to allow more space for the transaction log file to grow.