# Database usage by Project

**URL:** <https://forum.inductiveautomation.com/t/database-usage-by-project/104947>\
**Category:** Ignition\
**Tags:** database\
**Created:** [April 10, 2025, 1:08pm UTC](https://forum.inductiveautomation.com/t/database-usage-by-project/104947 "2025-04-10T13:08:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 10, 2025, 3:21pm UTC](https://forum.inductiveautomation.com/t/database-usage-by-project/104947/2 "2025-04-10T15:21:23Z")

</div>

This is essentially impossible to do because of the dynamic nature of Ignition in any other way than a "backwards" count via reference tracking at runtime, akin to the [Tag Reference Tracker](https://docs.inductiveautomation.com/docs/8.1/platform/tags/tag-diagnostics#tag-reference-tracker). We don't currently have any plans to add such a thing for databases, but it's a compelling idea that [folks have brought up before](https://forum.inductiveautomation.com/t/managing-named-queries/99484/2).

---

_[View the full topic](https://forum.inductiveautomation.com/t/database-usage-by-project/104947)._