# java.sql.SQLException after migration 7.9 to 8.1 and with SQL Server 2005 Database Connection

**URL:** <https://forum.inductiveautomation.com/t/java-sql-sqlexception-after-migration-7-9-to-8-1-and-with-sql-server-2005-database-connection/41526>\
**Category:** Ignition\
**Tags:** database, ignition80\
**Created:** [December 15, 2020, 3:31pm UTC](https://forum.inductiveautomation.com/t/java-sql-sqlexception-after-migration-7-9-to-8-1-and-with-sql-server-2005-database-connection/41526 "2020-12-15T15:31:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [December 15, 2020, 5:03pm UTC](https://forum.inductiveautomation.com/t/java-sql-sqlexception-after-migration-7-9-to-8-1-and-with-sql-server-2005-database-connection/41526/2 "2020-12-15T17:03:29Z")

</div>

The newer versions of the jdbc driver dropped support for the older versions. I ended up using jTDS for those.

[https://sourceforge.net/projects/jtds/files/](https://sourceforge.net/projects/jtds/files/)

EDIT: The reason I went this route was that M$ (bless their hearts) obfuscated download locations of their earlier versions of jdbc drivers, and I still needed to connect to later instance versions as well. So I added it as a separate driver.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/f/6f4421753fdfbd2215228aaba4b2a3677f736992.png)

---

_[View the full topic](https://forum.inductiveautomation.com/t/java-sql-sqlexception-after-migration-7-9-to-8-1-and-with-sql-server-2005-database-connection/41526)._
