I’m working on a client system that has an architecture like this:
When I setup the remote tag provider (On the front end), there was an option to change the “History Access Mode”.
I realize that if I change it to Database, then I can lower the traffic on the GAN, however with data going through a tag splitter I actually have 2 different data sources that I need to add and the configuration only give me one. Is there a trick I’m missing here? Or since we have a tag splitter there isn’t an ability to query the database directly for the historian data?
Or since we have a tag splitter there isn’t an ability to query the database directly for the historian data?
I do not think this is the case.
The expectation here is to target the Primary database the splitter uses. The splitter is duplicating the UPDATE/INSERT queries and sending to both databases, so having history access on DataBase #1 through the remote provider should give access to the same tag history one would expect in DataBase #2.
Except when the primary goes down…
I ended up doing a fail over database connection that seems to have made this work how we expected.