# Cannot create PoolableConnectionFactory v7.9.2 & SQL Server Express 2019

**URL:** <https://forum.inductiveautomation.com/t/cannot-create-poolableconnectionfactory-v7-9-2-sql-server-express-2019/59572>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [May 14, 2022, 3:32pm UTC](https://forum.inductiveautomation.com/t/cannot-create-poolableconnectionfactory-v7-9-2-sql-server-express-2019/59572 "2022-05-14T15:32:11Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [September 6, 2022, 7:56pm UTC](https://forum.inductiveautomation.com/t/cannot-create-poolableconnectionfactory-v7-9-2-sql-server-express-2019/59572/12 "2022-09-06T19:56:15Z")

</div>

I did mine with 7.9.12 and SQL 2016 back in June, since that we have tested with SQL 2019 on 7.9.12 in a different server(s), I used the same driver and didn't modify the class name, just left it as was

> [@Ms sql jdbc 7.9](https://forum.inductiveautomation.com/t/ms-sql-jdbc-7-9/60540):
>
> I am migrating data from MySQL to MS SQL, and getting a “can’t copy unknown to unknown” error in the script console. Searching the forum, other users have cleared this with a JDBC driver upgrade. I went for the latest one from the MS website (10.2.1.0) but after applying it, the connection to MS SQL was refused so I reverted to the previous one as it’s a live system. Looking into the error in the logs, searching forum again suggested to delete TLS 1 and 1.1 from the java.security file, however …

---

_[View the full topic](https://forum.inductiveautomation.com/t/cannot-create-poolableconnectionfactory-v7-9-2-sql-server-express-2019/59572)._
