# SQL Database became faulty after upgradation from V8.1.13 to V8.1.19 **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [August 22, 2022, 3:41pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277 "2022-08-22T15:41:48Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [August 22, 2022, 4:14pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277/5 "2022-08-22T16:14:22Z")
I would suggest taking a look at the following guide. The fix here may be as easy as upgrading the driver. If that doesn’t work though, I would suggest looking at the other options. Since you were on 8.1.13 which has TLSv1 and TLSv1.1 disabled by default, it’s possible someone had previously re-enabled those in the java security file which is why you were able to connect before upgrading to 8.1.19. I would highly suggest upgrading your SQL Server to support later versions of TLS and upgrading your JDBC driver instead of just re-enabling the older versions of TLS. > **[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)** > > Summary > A recent update to Java 8 (8u291), which also applies to Java 11.0.11 and above, has disabled TLS 1.0 and 1.1. This has resulted in cases of Ignition's connection to Microsoft SQL Server (M... --- _[View the full topic](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277)._