# Database Trigger Module

**URL:** <https://forum.inductiveautomation.com/t/database-trigger-module/84270>\
**Category:** Module Development\
**Tags:** perspective\
**Created:** [January 15, 2024, 2:39pm UTC](https://forum.inductiveautomation.com/t/database-trigger-module/84270 "2024-01-15T14:39:58Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Subin\_Adhikari](https://avatars.discourse-cdn.com/v4/letter/s/898d66/32.png) [@Subin\_Adhikari](https://forum.inductiveautomation.com/u/Subin_Adhikari)\
**Post date:** [January 15, 2024, 9:01pm UTC](https://forum.inductiveautomation.com/t/database-trigger-module/84270/6 "2024-01-15T21:01:42Z")

</div>

> [@Longest Recent Queries Trace](https://forum.inductiveautomation.com/t/longest-recent-queries-trace/37560/4):
>
> Correct. Just the logs. The long running query tracker has a hardcoded limit of 10 per datasource.

I wish this was not hardcoded for 10 per data source so that we can enable/disable it upon requirement.

I believe what I want to achieve is already built-in ignition with few limitations. Thank you so much, Ignition Team.

---

_[View the full topic](https://forum.inductiveautomation.com/t/database-trigger-module/84270)._