Remote Tag Provider with multiple History Datasources (not only one DB)
D
Dries Smeuninx
When configuring a Remote Tag Provider it's possible to access the historian database directly without using the gateway network.
When specifying multiple History Providers linked to separated databases, with for example different pruning ages or criticality (Gxp / non-gxp). It's possible to use those multiple History Providers in a Standard Tag Provider.
The problem today is that you can only configure one History Datasource on a Remote Tag Provider when accessing the database directly.
It would be nice if a [list] of History Providers could be configured, for example linked on index with a [list] of databases. So when querying data from the Remote Tag Provider all History Providers with corresponding databases are available via parameters.
Log In