# SQL Drivers for Ignition 8.0 beta

**URL:** <https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387>\
**Category:** Ignition Early Access\
**Created:** [February 6, 2019, 3:52pm UTC](https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387 "2019-02-06T15:52:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dholt](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dholt/32/4458_2.png) [@dholt](https://forum.inductiveautomation.com/u/dholt)\
**Post date:** [February 6, 2019, 3:52pm UTC](https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387/1 "2019-02-06T15:52:45Z")

</div>

![Untitled](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/492c08202e12576503b1b302ae4fdd03f1a42af4.jpeg)

Am I just missing something in installation? I cannot seem to connect at all to my SQL server, and the drivers that are needed, at least from walkthroughs that I’ve found, aren’t available with ignition 8?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 6, 2019, 3:56pm UTC](https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387/2 "2019-02-06T15:56:29Z")

</div>

JDBC drivers are in a bit of flux right now. Some are coming back, others will need to be installed but there will be a guided process.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [February 6, 2019, 3:58pm UTC](https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387/3 "2019-02-06T15:58:00Z")

</div>

Due to licensing requirements and distribution concerns, we are not able to distribute drivers for many SQL databases. Documentation in this regard can be found [here](https://docs.inductiveautomation.com/display/DOC80/JDBC+Drivers+and+Translators).

If this is a clean installation, then yes - you’ll need to download whatever driver you would need to connect to a database which is already in place. If this is an upgrade, then your driver should already be in place, and this would indeed be something we should be concerned about.

---

<div class="post-metadata">

**Author:** ![dholt](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dholt/32/4458_2.png) [@dholt](https://forum.inductiveautomation.com/u/dholt)\
**Post date:** [February 6, 2019, 3:59pm UTC](https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387/4 "2019-02-06T15:59:29Z")

</div>

I’m trying to install on locally, and not on our current server that already has running ignition gateway on it. Would it be advisable to install on existing server with active gateway and just designate a different port? Or no

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [February 6, 2019, 4:01pm UTC](https://forum.inductiveautomation.com/t/sql-drivers-for-ignition-8-0-beta/22387/5 "2019-02-06T16:01:57Z")

</div>

I’m a fan of separate machines, but the different port route should be a valid option. You just need to ask yourself if installing the necessary JDBC driver(s) is more of a headache than maintaining and remembering which Gateway is using which ports.