# Database Connection Faulting, Too Many Connections?

**URL:** <https://forum.inductiveautomation.com/t/database-connection-faulting-too-many-connections/89221>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [April 22, 2024, 4:48pm UTC](https://forum.inductiveautomation.com/t/database-connection-faulting-too-many-connections/89221 "2024-04-22T16:48:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [April 22, 2024, 6:03pm UTC](https://forum.inductiveautomation.com/t/database-connection-faulting-too-many-connections/89221/4 "2024-04-22T18:03:54Z")

</div>

> [@Colin\_Quinn](#):
>
> The view that is likely causing this is something that is currently refreshed when there is a specific set of actions, and refreshed for all current sessions. This refreshing of queries is used to build a table with some other subviews that also contain query bindings.

In addition to what @pturmel said, you should also try to eliminate as much traffic as possible. How many of these queries are returning filtered data of the original queried dataset? If possible instead of query bindings which return a subset of the original dataset, opt instead for an expression binding or property binding with transform to generate the filtered subset. This eliminates the extra trips to the DB and lessens the load.

Also, if you have/or can use Phil's [Integration Toolkit Module](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934) there are tools included that can make this type of task (filtering data) easier.

---

_[View the full topic](https://forum.inductiveautomation.com/t/database-connection-faulting-too-many-connections/89221)._