Active10 months ago

Jdbc Driver For Sql Server
Microsoft Jdbc Driver Sql Server
Microsoft Jdbc Driver For Sql
Jdbc

What are the differences between each driver? I mean, besides one of them being open-source

What are the pros / cons of each one?

Which one would you recommend?

Download the Microsoft JDBC Driver 6.4 for SQL Server, a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in Java Platform, Enterprise Editions.

here's jTDS own opinion on the subject: http://jtds.sourceforge.net/

Adam Wagner

11.7k4 gold badges46 silver badges63 bronze badges

Fixes a connection issue that occurs when you use JDBC Driver in a client application to connect to a SQL Server 2008 or a SQL Server 2008 R2 database. This issue occurs if the application is developed based on JRE version 6 Update 29 or a later version.
I-net software offers a full range of JDBC drivers for MS SQL Server Database. From this product line you can pick the driver that fits your requirements best; all MS SQL Server drivers are JDBC type 4 drivers, i.e., the drivers are completely written in Java and can be deployed on every platform.

opensasopensas

28.3k63 gold badges203 silver badges309 bronze badges

5 Answers

They are distinct implementations. The jTDS driver is a type 4 and in my experience has better performance. I have been using the jTDS driver in a production environment without any issues for 5 years.

I would recommend going with jTDS.

jzdjzd

21.8k7 gold badges49 silver badges75 bronze badges

While for many years jTDS was much superior than buggy mssql's own driver, the things are changing to the opposite recently.

Jdbc Driver For Sql Server

Free columns game. Here is qoute from https://confluence.atlassian.com/bitbucketserver/transitioning-from-jtds-to-microsoft-s-jdbc-driver-776640388.html:

Why change drivers?

Recent releases of Hibernate, which Bitbucket Server uses to simplify its persistence layer, have introduced a requirement that the JDBC drivers and connection pools used be JDBC4-compliant. JDBC4 was introduced with Java 6.

The jTDS driver used by releases prior to Bitbucket Server 2.1 is a JDBC3 driver, compatible with Java 1.3, and therefore cannot be used with newer versions of Hibernate. While jTDS 1.3.0 and 1.3.1 claim to implement JDBC4, and JDBC4.1, they actually don't. The new methods have been 'implemented', but their implementations are all throw new AbstractMethodError(), which means they can't actually be used. (See an example here, on GitHub.)

Since jTDS 1.3.1 does not provide a functioning JDBC4 implementation, the decision was made to replace jTDS with Microsoft's own SQL Server driver. Microsoft's driver is actively maintained, where jTDS hasn't been updated since 2014 (and prior to the small round of updates done in 2014 it hadn't been updated for multiple years). Microsoft offers a full JDBC4.2 (Java 8) driver and supports all the features of SQL Server, including SQL Server 2016.

VadzimVadzim

16.7k5 gold badges90 silver badges126 bronze badges

One relevant difference is, that the JDBC 4.0 Implementation of the JTDS-Driver (v1.3.1) requires at least Java 7, whereas the JDBC 4.0 Implementation of the Microsoft driver is available in Java 6.

This is important if you want to use Hibernate 4.3 (relying on JDBC 4.0 API) and support Java 6. In that case JTDS is not an option. Microsoft money 2007 download free.

felvhagefelvhage

The key reason FOR using jTDS is that it uses the lesser GPL license where Microsoft's driver uses their own license which has much more restrictions to it. One restriction of note is that you may not

work around any technical limitations in the software

There are more restrictions within the license such as:

transfer the software or this agreement to any third party
use the software for commercial software hosting services

Which could be interpreted that you may not use it in production code, however earlier points in the license seem to allow it.

Having said all of this, I don't know of the licenses within SQL Server itself which may or may not restrict third-party drivers such as jTDS connecting to it.

Microsoft Jdbc Driver Sql Server

Another point is that jTDS is available via maven, the Microsoft driver is not.

For my choice, use jTDS, it is more permissive and least likely to get you into trouble, and; it's a better driver.

Brett RyanBrett Ryan

Microsoft Jdbc Driver For Sql

15.4k25 gold badges109 silver badges140 bronze badges

jTDSperformance is good, but looks like the fail-over property is not supported by jTDS, if the SQL Server switches to secondary, needed to restart the application/server for picking the new ip and reseting the connection.

AnilAnil

Jdbc

Not the answer you're looking for? Browse other questions tagged javasql-serverjdbcjtds or ask your own question.

Mssql Support Jdbc Drivers