# Can I have two gateways using the same SQL database for historic logging?

**URL:** <https://forum.inductiveautomation.com/t/can-i-have-two-gateways-using-the-same-sql-database-for-historic-logging/56816>\
**Category:** Ignition\
**Created:** [March 4, 2022, 12:58am UTC](https://forum.inductiveautomation.com/t/can-i-have-two-gateways-using-the-same-sql-database-for-historic-logging/56816 "2022-03-04T00:58:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 4, 2022, 9:05pm UTC](https://forum.inductiveautomation.com/t/can-i-have-two-gateways-using-the-same-sql-database-for-historic-logging/56816/2 "2022-03-04T21:05:44Z")

</div>

Not a problem at all (as long as they have distinct gateway names).

The historian already uniquely identifies every record by what system and tag provider it came from.  
Check `sqlth_drv`, there will be at least two records (one `null`, one probably with an entry for `default`) for each gateway you connect to a given historian.

---

_[View the full topic](https://forum.inductiveautomation.com/t/can-i-have-two-gateways-using-the-same-sql-database-for-historic-logging/56816)._