The "ELM 411" - Improved Database Pruning
We all like to be more efficient - and like our systems to run at peak efficiency as well. As auditing and data volumes have increased, your ELM database has probably experienced a corresponding boost in size. This in-turn creates more work for the archiving and pruning tasks ELM performs.
To address this, the current release of ELM 5.5.141 has made improvements to the pruning technique it uses. Instead of one copy and delete operation, ELM now uses an Incremental Pruning approach.
ELM Pre-Build 141 |
ELM Build 141 |

Single Copy
|
Incremental Copy |
If archiving, ELM will bulk copy 5000 rows to the Archive database, and then delete 5000 rows from the Primary database. Then it will process the next 5000 rows, repeating until all older data is removed from the Primary database.
ELM Pre-Build 141 |
ELM Build 141 |

Single Delete
|

Incremental Delete
|
If just pruning, ELM will delete increments of 5000 rows at a time. This results in much shorter blocking, and smoother operation of your ELM Server and event collection.
If you haven't already, we highly encourage you to update to the latest release of ELM to take advantage of the new efficiencies in data management. Click Here to Download Now!
We hope that you found this article informative and wish you continued success with your ELM deployment!
NOTE: All ELM 411 articles are written based on ELM Version 5.5 and instructions may not be accurate for previous ELM Versions. If you would like assistance upgrading to ELM 5.5 so you can use these tips - please contact support@tntsoftware.com.
Share your own ELM tips!
Have a tip or trick with our ELM products you'd like to share with our newsletter subscribers? Send your ideas and any applicable screen shots to info@tntsoftware.com with "ELM 411" in the subject line. We'll take a look and if usable you'll see it published here in the ELM 411 section of upcoming newsletters!