# Cancel Journal Data through scripting

**URL:** <https://forum.inductiveautomation.com/t/cancel-journal-data-through-scripting/34911>\
**Category:** Ignition\
**Tags:** database, ignition80, scripting\
**Created:** [May 20, 2020, 1:42pm UTC](https://forum.inductiveautomation.com/t/cancel-journal-data-through-scripting/34911 "2020-05-20T13:42:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![betti.francesco](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/betti.francesco/32/6309_2.png) [@betti.francesco](https://forum.inductiveautomation.com/u/betti.francesco)\
**Post date:** [May 20, 2020, 1:42pm UTC](https://forum.inductiveautomation.com/t/cancel-journal-data-through-scripting/34911/1 "2020-05-20T13:42:42Z")

</div>

Hi all: because of DB size limitation, I need to implement a mechanism, other than the prune, to clear data by size, to keep the DB size within a certain threshold. The system.alarm.\* set of function seem not to be usefull for this purpose, so I believe the only way is to delete data from the Journal DB tables, correct? And if so, where could I find documentation on how are the various dbo.alarms\_\* tables related one each other?  
Many thanks in advance,  
Francesco