Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Access Rights Manager (ARM) formerly 8MAN > ARM - Knowledgebase Articles > Reduce SQL transaction log file

Reduce SQL transaction log file

Updated October 9, 2018


This article details how to reduce the SQL transaction log file through the basic configuration of ARM. For this, the configuration interface must be started.


  • Access Right Manager


It is recommended that SQL file reductions are completed when all ARM users are disconnected from the system.


  1. Click on the basic configuration icon.
  2. Click Recheck. A confirmation message "Configuration successfully loaded!" is displayed when recheck is complete.
  3. The buttons to the Recovery Model appear to change, or to zoom out, the database or SQL transaction log file:
    1. Switch to simple/full recovery mode
    2. Shrink the database log files
    3. Shrink all database
  4. Select the "DB Decrease logs" option. ARM reloads with the Decrease applied.
  5. (Optional) Set the retention period of scanned images in the database to a shorter interval.
    1. Start the configuration interface.
    2. Click on the menu server.
    3. Under Storage of Scans, specify the length of time Active Directory and File Server scans are to be stored in the database.

      The number of days for Active Directory can be unique, 180 days and 5 months. If you do not need 180 daily scans, set 30 days + 5 months, for a total of 6 months. Please note: when set to 30 days for the scans, the first month 29 days for the first month remains in the archive, and one day remain active. The database archive is then created and the data for the cleanup no longer exists.


If the Scan archive is turned on, scans that are not stored in the database are not lost and remain to be cleared in the scan archive. Data from the scan can archive, as well as scans that are still stored in the database, can be loaded at any time in ARM.


Last modified



Internal Use Only