# Whats best practice for multiple connections to the same database

**URL:** <https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498>\
**Category:** Ignition\
**Tags:** ignition81, database\
**Created:** [May 13, 2026, 1:17am UTC](https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498 "2026-05-13T01:17:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\
**Post date:** [May 13, 2026, 1:17am UTC](https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498/1 "2026-05-13T01:17:45Z")

</div>

One of our sites is running 8.1.44, has one database and a multiple connections to that database. One connection per project for a total of about 30+ ish.

Going back to my 7.7 days, I recall this being an issue with the way the tag history is stored, tables being locked, and a few other things as the connections to the tables were not aware of each other.

From my understanding, they just wanted to control the database access to each project, no other reason for the multiple connections.

Before I tell them that they should consolidate their db connections, I wanted to make sure my information is accurate.

Are there any issues having the 30+ connections to the same database and tables?

---

<div class="post-metadata">

**Author:** ![Jasmine\_Quick](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jasmine_quick/32/80380_2.png) [@Jasmine\_Quick](https://forum.inductiveautomation.com/u/Jasmine_Quick)\
**Post date:** [May 13, 2026, 1:54am UTC](https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498/2 "2026-05-13T01:54:21Z")

</div>

Are you saying there are 30 database connections configured in the gateway, all pointing to the same database?

An issue i've come across is that if you have duplicate connections to the same gateway, and one has pruning, the prune doesn't recognise the different "connection", and will apply to all pf the Ignition tables. Differences in the sectioning (ie weekly/monthly) can also cause trouble.

Additionally, this also just sounds painful to manage?

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [May 13, 2026, 9:45am UTC](https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498/3 "2026-05-13T09:45:11Z")

</div>

It's possible to have multiple schemas within the same database for different purposes, and each schema can be connected to Ignition using separate connections without any issues. I wouldn't expect any problems even with around 30 separate schemas. However, if we're talking about 30 separate connections to the same schema and tables, I would need to hear the reasoning behind this before I would consider accepting it.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 13, 2026, 11:24am UTC](https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498/4 "2026-05-13T11:24:47Z")

</div>

> [@drewdin](#):
>
> Are there any issues having the 30+ connections to the same database and tables?

Yes, because every configured database connection is actually a **pool** of connections, eight by default. So, unless you've tailored that, your 30+ connections is really 240+ on the DB side. That can be a real disaster for DB resource management, as they will all have the same priority.

> [@drewdin](#):
>
> control the database access to each project

This is a terrible reason, as there's no "control" separating the projects' access to each others' databases.

---

<div class="post-metadata">

**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\
**Post date:** [May 13, 2026, 12:05pm UTC](https://forum.inductiveautomation.com/t/whats-best-practice-for-multiple-connections-to-the-same-database/115498/5 "2026-05-13T12:05:51Z")

</div>

I agree, I have an email ready to send to the site explaining the issues but I didn't want to say it was bad. I wanted to explain why they should consolidate the connections.

I appreciate the info!
