40 isn't too many, but if you're able to estimate that, it's unclear to me why you can't just set these up in advanced instead of using system.db.addDatasource. Where are you going to get all the information you need to make the connection and what part of the workflow would that happen in?
Is there a number that might seem to many? I'm new to 40 connections.
As I understand, there is a pattern that depends on the date; a new database per month.
There are two approaches here:
Keep adding databases ever month. Meaning that 40 is just the current number and that it will continue to grow.
Dump their "legacy" way of doing things. That would keep it a 40 and I will have a fixed array of names to add as connections in the gateway. I find system.db.addDatasource handy in this scenario.
Case #1; Before attempting to read I should make sure the connection is established. Hopefully the names do follow a pattern and no surprises are waiting for me. It can be a scheduled event in the gateway or a component input if there are surprises.
Case #2: it just have to be setup once. I hope for this case.
I was as surprised as everyone else here. My question was "why??" but I got no answer at that time.
Yeap, new database...
I wish.
And... that was finally the answer. After my initial shock, I quit complaining and now I'm just moving with the flow.
--
So I need a completely new connection to each database to display the data. What can/might be the upper limit regarding database connections? That sole server has 40 databases and I have a few databases for Ignition (historian, alarms, audit).
Would you advice to do it manually? Some security concerns? something else?