# Connecting to QuestDB **URL:** \ **Category:** Ignition\ **Created:** [May 3, 2023, 1:10pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199 "2023-05-03T13:10:51Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![coffeyr](https://avatars.discourse-cdn.com/v4/letter/c/9fc348/32.png) [@coffeyr](https://forum.inductiveautomation.com/u/coffeyr)\ **Post date:** [May 3, 2023, 1:10pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/1 "2023-05-03T13:10:52Z")
We are looking to connect to a QuestDB instance that is set up on the same server as our gateway. Has anyone done this before that could offer any pointers? ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [May 3, 2023, 1:14pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/2 "2023-05-03T13:14:10Z")
You'll need to add the QuestDB JDBC driver when setting up the connection. [JDBC Drivers and Translators - Ignition User Manual 8.1 - Ignition Documentation (inductiveautomation.com)](https://docs.inductiveautomation.com/display/DOC81/JDBC+Drivers+and+Translators) ---
**Author:** ![Jay\_Jain](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@Jay\_Jain](https://forum.inductiveautomation.com/u/Jay_Jain)\ **Post date:** [December 3, 2024, 12:21pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/3 "2024-12-03T12:21:02Z")
Hi, I am also facing this issue. I have connected a questdb instance with Ignition. It shows a valid connection in database connection status page of the Gateway. However when selecting tags and enabling tag history to questdb. No data is logged. I changed the database to a MS SQL instance it started instantly logging. Any suggestions? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/afcf9b8db41ac6b87a64ef1134803fcb3d0ec9f6.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/f/9fdf5616a8ed4af48a13fad2f9de5a412dfc13b3.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/4/d45b24e95a1dcee6fb74706c0bbe58bd93270736.png) ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [December 3, 2024, 4:45pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/4 "2024-12-03T16:45:28Z")
Since you're using Maker edition, I'm guessing this may not be immediately important, but Ignition 8.3 being released sometime early next year will natively use QuestDB as it's historian provider out of the box. ---
**Author:** ![djs](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@djs](https://forum.inductiveautomation.com/u/djs)\ **Post date:** [December 3, 2024, 5:35pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/5 "2024-12-03T17:35:26Z")
Quest DB is not a relational database even though it supports a SQL like language. It is a timeseries database. Since Ignition's SQL historian requires (non timestamp) primary keys and foreign keys, I would not expect Quest DB to work well with it. Quest DB's is designed for timeseries data and handles it very efficiently. However, because it is fundamentally a different technology, you have to redesign your DB tables to leverage its power. For example, its "primary key" equivalent would be the [designated timestamp](https://questdb.io/docs/concept/designated-timestamp/), it has a [symbol](https://questdb.io/docs/concept/symbol/) datatype that could pretty much replace the sqlth\_te table, it also has built it partitioning based on its designated timestamp column. You could essentially almost have a "single table" historian. Trying to use it as a relational database would mean to not leverage any of the design decisions that make it performant in the first place. If you want to utilize Quest DB as a historian, I'd wait for 8.3's Power Historian. ---
**Author:** ![Marcus\_Sysum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcus_sysum/32/57944_2.png) [@Marcus\_Sysum](https://forum.inductiveautomation.com/u/Marcus_Sysum)\ **Post date:** [December 3, 2024, 7:55pm UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/6 "2024-12-03T19:55:27Z")
Look at this post below for more information why the current tag historian doesn't work with quest even though the postgres driver will connect to it. > [@Quest Database connection](https://forum.inductiveautomation.com/t/quest-database-connection/78246): > > Trying to use Quest Database as Historian DB . i am able to build connection using JDBC drive .able to read from preconfigured Table . But , Ignition failed to write to the DB showing below errors when Ignition trying to create Tables for Historian . any advise on that .. Do we need to create special translator for Quest DB ? ---
**Author:** ![Jay\_Jain](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@Jay\_Jain](https://forum.inductiveautomation.com/u/Jay_Jain)\ **Post date:** [December 4, 2024, 10:11am UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/7 "2024-12-04T10:11:57Z")
Yes, this is something I have been testing for my own curiosity. Anyways, Ignition with questdb as OOTB sounds wonderful. ---
**Author:** ![Jay\_Jain](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@Jay\_Jain](https://forum.inductiveautomation.com/u/Jay_Jain)\ **Post date:** [December 4, 2024, 10:12am UTC](https://forum.inductiveautomation.com/t/connecting-to-questdb/73199/8 "2024-12-04T10:12:39Z")
Agree. That is what I have been thinking. But thanks for providing the details. > [@Marcus\_Sysum](#): > > Look at this post below for more information why the current tag historian doesn't work with quest even though the postgres driver will connect to it. Got it. Thanks for the info.