# 3rd Party Data Historians **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 6, 2023, 2:10pm UTC](https://forum.inductiveautomation.com/t/3rd-party-data-historians/74637 "2023-06-06T14:10:27Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![m.boog](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@m.boog](https://forum.inductiveautomation.com/u/m.boog)\ **Post date:** [June 6, 2023, 2:10pm UTC](https://forum.inductiveautomation.com/t/3rd-party-data-historians/74637/1 "2023-06-06T14:10:27Z")
We had a potential customer reach out to us today asking about interfacing Ignition with 3rd party data historians. They asked specifically about Canary, which is a NoSQL historian that accepts SQL commands. I assume I couldn't interface to Canary through the Tag History DB Table Historian Provider, as Canary doesn't have actual SQL tables, even thought it can be queried with SQL - is that a correct assumption? Does anybody have any recommendations for 3rd party data historians that play well with Ignition? Thanks in advance for the time! ---
**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:** [June 6, 2023, 2:11pm UTC](https://forum.inductiveautomation.com/t/3rd-party-data-historians/74637/2 "2023-06-06T14:11:55Z")
Canary has a Tag Historian driver for Ignition. 😁 Drop it in and use it seamlessly, as far as I can tell. ---
**Author:** ![m.boog](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@m.boog](https://forum.inductiveautomation.com/u/m.boog)\ **Post date:** [June 6, 2023, 3:08pm UTC](https://forum.inductiveautomation.com/t/3rd-party-data-historians/74637/3 "2023-06-06T15:08:22Z")
Wow, that's a spiffy-looking integration. Thanks for pointing me in the right direction.