# SQL Server Connection Faulted **URL:** \ **Category:** Ignition\ **Tags:** database, ignition79\ **Created:** [May 5, 2021, 6:46pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393 "2021-05-05T18:46:27Z")\ **Posts on this page:** 5\ **Page:** 3
**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\ **Post date:** [November 21, 2022, 6:51pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/42 "2022-11-21T18:51:42Z")
This started with version 10.2 of Microsoft's JDBC Driver. You can also add `trustServerCertificate=true` or set up an SSL Certificate on the SQL Server Instance. The [TLS v1.0 and v1.1 Microsoft SQL Server Database connection issue](https://support.inductiveautomation.com/hc/en-us/articles/4417310204813-TLS-v1-0-and-v1-1-Microsoft-SQL-Server-Database-connection-issue) article has been updated to include that information. For anyone running into the TLS issue, I would suggest verifying your database version just doesn't support TLS v1.2 before re-enabling the older versions. In a lot of cases the only change that's needed is to upgrade the JDBC driver which is also mentioned and explained in the article. ---
**Author:** ![ematschke](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ematschke/32/7544_2.png) [@ematschke](https://forum.inductiveautomation.com/u/ematschke)\ **Post date:** [August 29, 2023, 7:02pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/43 "2023-08-29T19:02:54Z")
with Ignition 8.1.27 I edited the java.security file (in the ignition folder, not the old Java folder) the same way that Kraenbring shows. Then restarted the gateway using gwcmd. I did some other stuff, and now not exactly sure what all I did to get it going, but now i have "Valid" connection to my MSSQL. Thanks @pturmel ---
**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 29, 2023, 7:19pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/44 "2023-08-29T19:19:07Z")
Hopefully this is just a temporary measure until you've upgraded whatever ancient version of MSSQL you're connecting to 🤞 ---
**Author:** ![Xavier\_Medina\_Macias](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/xavier_medina_macias/32/52112_2.png) [@Xavier\_Medina\_Macias](https://forum.inductiveautomation.com/u/Xavier_Medina_Macias)\ **Post date:** [September 11, 2023, 3:26pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/45 "2023-09-11T15:26:48Z")
Thank You, This worked for me too. I'm upgrating between 7.9 to 8.1.31 Ignition's versions and had been the same trouble. First, I changed the Allows control over the file java.security for delete the "TLSv1, TLSv1.1" sentences. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/7/87c4fe7883f3b6d26056059177e5c3b7dcc57cdf.png) Second, I update the version of the JDBC controller (mssql-jdbc-12.4.0.jre11) following these prompts [Releases · microsoft/mssql-jdbc · GitHub](https://github.com/microsoft/mssql-jdbc/releases)[JDBC Drivers and Translators - Ignition User Manual 8.0 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC80/JDBC+Drivers+and+Translators) Finally, I verify the Database Connections on the gateway and It was on Valid status ---
**Author:** ![jacque\_trahan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jacque_trahan/32/58886_2.png) [@jacque\_trahan](https://forum.inductiveautomation.com/u/jacque_trahan)\ **Post date:** [January 11, 2024, 6:35pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/46 "2024-01-11T18:35:23Z")
This helped a lot but I could not get the Option 1, the more Secure way, ff doing this for MSSQL. I downloaded the newest version yesterday and my version of ignition is from last week download. I had to use Option 2 and go to the java.security file and delete the TLSv1, TLSv1.1 text, save, then stop and restart ignition. The highlighted section below is what I deleted to get it to connect. Also, the information for option 1 from [Microsoft](https://learn.microsoft.com/en-US/troubleshoot/sql/database-engine/connect/tls-1-2-support-microsoft-sql-server#how-to-know-whether-you-need-this-update) does seem to deal with the _PoolableConnectionFactory_ ignition issue, or I might have missed. If anyone has a Step by step for the step 1 option please let me know. I want to make a video on that process for co-workers. I rather be more secure than use option two but my work is not for a client. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/b/6b45e76c63800b5f763f2bdb65dcfb27600d6947.png) [Previous page](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393.md?page=2)