How to reduce size of revision history database (Trial & Platform)

Note: This article applies only to Leapwork Trial and Leapwork Platform installations that use the local SQLite database. It does not apply to Leapwork Enterprise, which stores data in Microsoft SQL Server.

Every time an asset is saved, the Controller creates a new (numbered) version of the asset, this process is stored in the revision history database. Due to multiple updates/changes to the flows/sub-flows/captures, the size of the revision history database grows fast, which can lead to low memory availability on the controller machine.

The user can follow the below steps and safely deallocate memory used by the revision history database:

1. Stop Controller service
   • Press Win+R combination to open the Run dialog
   • Type ‘services.msc’ and press Enter to open Services window
   • Find Leapwork Controller and stop it using the right mouse button click and “Stop” command.
2. Take Full Backup - Platform & Trial Version.
3. Remove 'LEAPWORK.DB.RevisionHistory.sqlite' database
4. Start Controller
   • Press Win+R combination to open the Run dialog
   • Type ‘services.msc’ and press Enter to open Services window
   • Find Leapwork Controller and start it using the right mouse button click and “Start” command.

After restarting the controller service, the new 'LEAPWORK.DB.RevisionHistory.sqlite' database will be created automatically and disk space will be free.

Note: User will lose old revision history after the above database is deleted and new history will be created.

For any clarification, please contact our Priority Support.