Whats best practice for multiple connections to the same database

Ignition
,
1

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?

2

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?