# GAN Remote Tag Provider History Access

**URL:** <https://forum.inductiveautomation.com/t/gan-remote-tag-provider-history-access/56335>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [February 19, 2022, 5:00pm UTC](https://forum.inductiveautomation.com/t/gan-remote-tag-provider-history-access/56335 "2022-02-19T17:00:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\
**Post date:** [February 19, 2022, 5:00pm UTC](https://forum.inductiveautomation.com/t/gan-remote-tag-provider-history-access/56335/1 "2022-02-19T17:00:11Z")

</div>

I’m working on a client system that has an architecture like this:

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/b/db633a72b5d5e704bdd51ad901e6296e6e0545a7.png)

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?

---

<div class="post-metadata">

**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\
**Post date:** [March 2, 2022, 5:16pm UTC](https://forum.inductiveautomation.com/t/gan-remote-tag-provider-history-access/56335/2 "2022-03-02T17:16:42Z")

</div>

> 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.

---

<div class="post-metadata">

**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\
**Post date:** [March 2, 2022, 5:22pm UTC](https://forum.inductiveautomation.com/t/gan-remote-tag-provider-history-access/56335/3 "2022-03-02T17:22:15Z")

</div>

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.