# MSSQL 2022 Compatibility **URL:** \ **Category:** Ignition\ **Tags:** database, ignition81, perspective\ **Created:** [July 1, 2022, 2:17pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434 "2022-07-01T14:17:03Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [July 1, 2022, 2:17pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/1 "2022-07-01T14:17:03Z")
Client is requesting the latest MSSQL version, 2022, any known compatibility issues with Ignition? I assume no, but thought it was worth an ask. ---
**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:** [July 1, 2022, 2:23pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/2 "2022-07-01T14:23:21Z")
If anything you might need a newer JDBC driver, but otherwise I’d expect it to work. SQL Server 2022 is not yet in the [support matrix](https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-ver16) I always refer people to. It seems it’s not fully released yet, only in Public Preview. ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [July 1, 2022, 2:35pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/3 "2022-07-01T14:35:01Z")
Thanks, I just noticed it isn’t fully released. ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [April 6, 2023, 9:35pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/4 "2023-04-06T21:35:12Z")
@Kevin.Herron it appears it is now in the support matrix, however, it looks like IA doesn't have it listed here, [Database Connections - Ignition User Manual 8.1 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC81/Database+Connections#DatabaseConnections-SupportedDatabasesinIgnition) Is 2022 fully supported? I'm asking because my answer means a lot less than yours. The client wants that warm fuzzy that only you can provide. 🙂 ---
**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:** [April 6, 2023, 9:52pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/5 "2023-04-06T21:52:45Z")
I've pinged the QA team... I'll let you know if there's any warm fuzzies to be had here. ---
**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:** [April 6, 2023, 10:04pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/6 "2023-04-06T22:04:45Z")
No warm fuzzies ☹ Not to say it doesn't work, just that they're still using 2019 in their test setup right now. FWIW, I think not everything in the support matrix has necessarily been tested / is tested... some of them maybe just be listing what the JDBC driver claims support for. ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [July 17, 2024, 12:45pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/7 "2024-07-17T12:45:26Z")
@Kevin.Herron We are moving forward to SQL Server 2022 upgrades over the next few months, any updates or issues to note? Thanks! ---
**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:** [July 17, 2024, 12:53pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/8 "2024-07-17T12:53:17Z")
I wouldn't expect any issues... just make sure your JDBC driver is one listed as supporting 2022 in the compatibility matrix I linked to above. ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [July 17, 2024, 2:13pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/9 "2024-07-17T14:13:15Z")
I just checked "C:\Program Files\Inductive Automation\Ignition\user-lib\jdbc" and I am running "mssql-jdbc-7.2.1.jre11" The gateway was an early version 7 that has been upgraded over the years and is now 8.1.17. Looks like I need at least 12.2 for compatibility, I'll have to update the jdbc. ---
**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\ **Post date:** [July 17, 2024, 3:40pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/10 "2024-07-17T15:40:15Z")
FWIW, we're using SQL Server 2022 for a full-blown MES currently and haven't run into issues that have to do with the driver or some unsupported feature. Not that we test everything extensively, we just haven't seen anything in normal to moderately-heavy use. ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [July 17, 2024, 3:46pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/11 "2024-07-17T15:46:28Z")
which jdbc are you using and which version of ignition are you running? ---
**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\ **Post date:** [July 17, 2024, 4:00pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/12 "2024-07-17T16:00:14Z")
I didn't even really take that into consideration - I either used the jdbc driver that was included with Ignition or the one they link to in their docs. I'm using Ignition version 8.1.38 or so, but we've used it down to 8.1.16 (though it probably works with earlier versions). ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [July 17, 2024, 4:13pm UTC](https://forum.inductiveautomation.com/t/mssql-2022-compatibility/61434/13 "2024-07-17T16:13:57Z")
This server was version 7.X and upgraded to version 8.1.17 over time. From reading the docs, it doesn't update jdbc's for backwards compatibility, but if I'm updating the database I need to update the jdbc to match.