# Using DB Table Historian as history provider for edge sync services

**URL:** <https://forum.inductiveautomation.com/t/using-db-table-historian-as-history-provider-for-edge-sync-services/76700>\
**Category:** Ignition\
**Created:** [July 21, 2023, 11:03am UTC](https://forum.inductiveautomation.com/t/using-db-table-historian-as-history-provider-for-edge-sync-services/76700 "2023-07-21T11:03:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eskil\_Holum](https://avatars.discourse-cdn.com/v4/letter/e/cdc98d/32.png) [@Eskil\_Holum](https://forum.inductiveautomation.com/u/Eskil_Holum)\
**Post date:** [July 21, 2023, 11:03am UTC](https://forum.inductiveautomation.com/t/using-db-table-historian-as-history-provider-for-edge-sync-services/76700/1 "2023-07-21T11:03:32Z")

</div>

Hi, we have a database we use to log several different locations, to segregate the data a bit i wanted to use the DB Table historian to give each remote provider a different provider, but it seems like theese providers refuse connection.  
Am i trying to do something that is not supported, everything works when i use the direct Datasource History Provider.

---

<div class="post-metadata">

**Author:** ![Eskil\_Holum](https://avatars.discourse-cdn.com/v4/letter/e/cdc98d/32.png) [@Eskil\_Holum](https://forum.inductiveautomation.com/u/Eskil_Holum)\
**Post date:** [July 21, 2023, 11:25am UTC](https://forum.inductiveautomation.com/t/using-db-table-historian-as-history-provider-for-edge-sync-services/76700/2 "2023-07-21T11:25:37Z")

</div>

Ok, it seems like the DB table historian was not what i tought it was. To achieve the result i want i think i would have to split the SQL server into multiple DBs and set up several connections to the same database.

---

<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:** [July 21, 2023, 12:05pm UTC](https://forum.inductiveautomation.com/t/using-db-table-historian-as-history-provider-for-edge-sync-services/76700/3 "2023-07-21T12:05:00Z")

</div>

As long as each remote edge gateway has a unique name, Ignition will keep track of them within its metadata. You might want to have support look over your shoulder to set this up the first time.