# Forwarding historian data across gateway network

**URL:** <https://forum.inductiveautomation.com/t/forwarding-historian-data-across-gateway-network/115032>\
**Category:** Ignition\
**Tags:** database\
**Created:** [April 13, 2026, 3:25am UTC](https://forum.inductiveautomation.com/t/forwarding-historian-data-across-gateway-network/115032 "2026-04-13T03:25:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![will\_schreiner](https://avatars.discourse-cdn.com/v4/letter/w/6de8d8/32.png) [@will\_schreiner](https://forum.inductiveautomation.com/u/will_schreiner)\
**Post date:** [April 13, 2026, 3:25am UTC](https://forum.inductiveautomation.com/t/forwarding-historian-data-across-gateway-network/115032/1 "2026-04-13T03:25:41Z")

</div>

Hello,

I am in the process of trying to see how to best utilize the gateway network to move data from individual gateways to a central gateway and to SQL database connected to it. This is still early testing, so this is a basic example; but each site would it’s own (local) tag historian. I would like to use the ignition gateway network to then transfer the time series data up to the central gateway where it is then stored in a SQL database to be used in other applications.

I am currently wondering if this setup would be possible with a historian splitter and a remote historian.

At this point I am still exploring my options on how this would best be achieved and I was curious what some of the best ways there are to go about this.

---

<div class="post-metadata">

**Author:** ![Sanganak\_Kasare](https://avatars.discourse-cdn.com/v4/letter/s/8c91f0/32.png) [@Sanganak\_Kasare](https://forum.inductiveautomation.com/u/Sanganak_Kasare)\
**Post date:** [April 13, 2026, 8:29am UTC](https://forum.inductiveautomation.com/t/forwarding-historian-data-across-gateway-network/115032/2 "2026-04-13T08:29:03Z")

</div>

Hi Will,

To achieve this in the past, I’ve set up a History Splitter on the local gateways to separate local and central history storage (using remote history provider).

On the central gateway, I then create a Remote Tag Provider and configure its History Access Mode to Database, pointing it at the central historian database. This ensures that tag history is replicated across the gateway network, but all history queries are served locally from the central database, rather than being proxied back to the local gateways.

This approach significantly reduces gateway network traffic and improves client query performance.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 13, 2026, 1:34pm UTC](https://forum.inductiveautomation.com/t/forwarding-historian-data-across-gateway-network/115032/3 "2026-04-13T13:34:37Z")

</div>

> [@Sanganak\_Kasare](#):
>
> This approach

💯