# Old JDBC Driver On Gateway **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [August 27, 2026, 6:30pm UTC](https://forum.inductiveautomation.com/t/old-jdbc-driver-on-gateway/116925 "2026-08-27T18:30:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Zachary\_Kacel1](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@Zachary\_Kacel1](https://forum.inductiveautomation.com/u/Zachary_Kacel1)\ **Post date:** [August 27, 2026, 6:30pm UTC](https://forum.inductiveautomation.com/t/old-jdbc-driver-on-gateway/116925/1 "2026-08-27T18:30:48Z")
We need to start doing Windows based Auth for our SQL servers and found a video on Inductive University on how to set this up. In the process of walking through it I noticed our Ignition Server(8.3.6) has` mssql-jdbc-7.2.1.jre11.jar` this seems like an old driver. Should I be updating this driver on our server and if so, do Gateway updates not update this driver? Also if I should update the driver what rev should I use? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/b/5bbd719b2fcda8758bcbecd7fc86c6a3f028f9fb.png) > **[Connecting to SQL Server with Windows Login Video at Inductive University](https://inductiveuniversity.com/videos/connecting-to-sql-server-with-windows-login/8.3)** > > Learn about the files and configuration changes that are required to connect to Microsoft SQL Server using Windows credentials. ---
**Author:** ![Bushmatic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bushmatic/32/87014_2.png) [@Bushmatic](https://forum.inductiveautomation.com/u/Bushmatic)\ **Post date:** [August 27, 2026, 9:52pm UTC](https://forum.inductiveautomation.com/t/old-jdbc-driver-on-gateway/116925/2 "2026-08-27T21:52:30Z")
I believe gateway updates carry forward your existing drivers, and if you delete the old driver (by deleting the .jar file in user-lib/jdbc within the installation directory), Ignition will default to using the bundled driver (9.4.0.jre11) after a restart. The bundled driver is at the system level, and your screenshot shows the core level. What I would do is take a gateway backup, stop the gateway service, make a backup copy of your `mssql-jdbc-7.2.1.jre11.jar` file somewhere else and remove it from your installation directory, start the gateway service, then check config -\> databases -\> drivers for the Microsoft SQLServer JDBC driver (making sure it is 9.4.0.jre11). Check that all your SQL connections show as valid. From here I believe you could move into the Windows authentication portion. > [@Database Driver corrupted, now cannot open the Databases/Driver page](https://forum.inductiveautomation.com/t/database-driver-corrupted-now-cannot-open-the-databases-driver-page/67180/2): > > You can delete the JDBC driver file from the $IGNITION/user-lib/jdbc folder and restart the Ignition Gateway. > **[JDBC Drivers | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/jdbc-drivers)** > > Bundled JDBC Driver Modules > **[MSSQL​ - JDBC Driver and Database Translator Settings | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/platform/database-connections/connecting-to-databases/jdbc-drivers-and-translators/jdbc-driver-and-database-translator-settings#mssql)** > > This page details various JDBC driver and translator settings. See the JDBC Drivers and Translators page for information on adding and configuring JDBC drivers and translators. The settings listed below can be found by expanding the three dots menu... ---
**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:** [August 27, 2026, 10:36pm UTC](https://forum.inductiveautomation.com/t/old-jdbc-driver-on-gateway/116925/3 "2026-08-27T22:36:26Z")
This is great advice. Note that this behavior, with the bundled JDBC driver files inside modules, is something new to 8.3. We're hoping to achieve a sane balance between keeping the drivers up to date and not risking breaking folk's systems quietly on upgrade. In all prior versions, the seeded JDBC drivers when you _first_ installed were what you got in your gateway for the rest of time (and indeed, that's still the case if you're upgrading from older systems). Only _brand new_ gateways, starting on 8.3 fresh, will be subject to us automatically upgrading the driver underneath you when the modules update. Unless you choose to copy from the 'system' collection to 'core', at which point you'll be in the same situation as all prior versions. ---
**Author:** ![Zachary\_Kacel1](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@Zachary\_Kacel1](https://forum.inductiveautomation.com/u/Zachary_Kacel1)\ **Post date:** [August 28, 2026, 10:47am UTC](https://forum.inductiveautomation.com/t/old-jdbc-driver-on-gateway/116925/4 "2026-08-28T10:47:09Z")
Thank you. We are going to give this a shot on our QA Server first. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [August 28, 2026, 11:56am UTC](https://forum.inductiveautomation.com/t/old-jdbc-driver-on-gateway/116925/5 "2026-08-28T11:56:57Z")
I'll take a moment to chime in and say that you may have to stick with the latest supported jar for your instance of SQL Server. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/6/c6cbb226715a639a088f9c4a6568247f58f1f112.png) A later one would likely work with anything down to 2012, but... Microsoft. 🤷