# Ancient JDBC driver for MSSQL on Docker version **URL:** \ **Category:** Ignition\ **Tags:** docker\ **Created:** [August 2, 2024, 12:47pm UTC](https://forum.inductiveautomation.com/t/ancient-jdbc-driver-for-mssql-on-docker-version/94113 "2024-08-02T12:47:48Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Matej\_Medvecky](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej\_Medvecky](https://forum.inductiveautomation.com/u/Matej_Medvecky)\ **Post date:** [August 2, 2024, 12:47pm UTC](https://forum.inductiveautomation.com/t/ancient-jdbc-driver-for-mssql-on-docker-version/94113/1 "2024-08-02T12:47:48Z")
EDIT: The whole trouble was caused by restoring an old gateway backup and has nothing to do with the docker image as such. Hi everybody, I spent a few days looking for the issue that caused Ignition in Docker (8.1.42) to not connect to the MSSQL Server (2022) on the Windows 11 host (_no appropriate protocol_ error). I read all the articles and forum posts available on this topic, but nothing helped. I thought the issue was caused by running Docker in a Hyper-V VM and that the virtual network was somehow misconfigured. Recently, I found out that the default JDBC driver for MSSQL in the latest Docker image (8.1.42) is outdated: sqljdbc4.jar. I wasn't expecting it, and I checked it as the very last option (my fault). As soon as i enabled the tls 1.1 and 1.2 in java.security, it started to work. I also installed the same Ignition version on the host (Windows 11), and it connected to the same MSSQL server without any issues. This made me even more confused until I discovered that the JDBC driver on the host was up-to-date: mssql-jdbc-9.4.0.jre11.jar. Here is a screenshot from Docker: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/7/17b28e7b9dd8a60ed56fd85edd2b62dc0da3a09b.png) I am posting this here to save time for others. It would probably be great to update the Docker image as well. ---
**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:** [August 2, 2024, 1:05pm UTC](https://forum.inductiveautomation.com/t/ancient-jdbc-driver-for-mssql-on-docker-version/94113/2 "2024-08-02T13:05:40Z")
I think you'll find it was the JDBC driver in the backup you restored that was out of date, not the one in the docker image. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/4/64244e9b6572c1e020db144c1989779cc363d125.png) ---
**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:** [August 2, 2024, 1:35pm UTC](https://forum.inductiveautomation.com/t/ancient-jdbc-driver-for-mssql-on-docker-version/94113/3 "2024-08-02T13:35:33Z")
Well, 9.4 is also quite old. If you are trying to keep support for SQL Server 2012, the better driver would be 10.2. I think the user should be responsible for downgrading for older databases, not upgrading for newer. IA should ship mssql-jdbc-12.8, IMNSHO. > **[Support matrix - JDBC Driver for SQL Server](https://learn.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-ver16)** > > This page contains the support matrix and support life-cycle policy for the Microsoft JDBC Driver for SQL Server. ---
**Author:** ![Matej\_Medvecky](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej\_Medvecky](https://forum.inductiveautomation.com/u/Matej_Medvecky)\ **Post date:** [August 2, 2024, 4:18pm UTC](https://forum.inductiveautomation.com/t/ancient-jdbc-driver-for-mssql-on-docker-version/94113/4 "2024-08-02T16:18:59Z")
Yeah, you're absolutely right, my apologies, i didn't realize this. Thanks for clarifying it.