SQL Server with JTDS

Has anyone had success using JTDS to connect to MS SQL Server or Sybase? I have client tools working without issue, but, can not seem to get it to work in Snaplogic with the same configuration using JDBC. Please advise.

Hello ronmwhite,

Thank you for posting to our Community! Which version of the jTDS driver are you referring to? Is it the old/original one from SourceForge or a different one from GitHub? In addition, it would help to know what versions of SQL Server and Sybase you’re trying to connect to.

Is there one better than SourceForge and/or do you have a recommendation? It seems to work well. My config follows. Thoughts?

Microsoft SQL Server
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase

While we might suggest or showcase certain 3rd party drivers that can meet certain needs, we typically do not go as far as to recommend one over another as it really depends on what your needs are and if the driver meet those needs.

What I can share with you from working with the jTDS driver in past scenarios is that the latest version, 1.3.1, which you’re using, is no longer being developed by that team through SourceForge as of 2008. That specific version officially only supports up to SQL Server version 2012.

For SQL Server, have you considered using a JDBC driver from Microsoft? You can find their options at https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-ver15.

For Sybase, they have some JDBC suggestions at http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01776.1600/doc/html/san1357754910584.html as well.

JTDS still ships with and is used by default with a lot of tools but I digress. I have tools working with JTDS on the same machine where my groudplex is installed yet I can not get it to work with Snaplogic and was hoping to do so. I will continue to experiment.

Have you added it to the account in the JDBC JARs file section or are you trying to reference it from on the node itself? The screenshot below is for the Generic JDBC account type, though the SQL Server account type also has the field available.