6

Currently we use jtds for connecting to our SQL Server databases. I've always taken it for granted that we use it due to performance and reliability reasons, however, it's usage pre-dates my employment.

All of that being said, we are now playing with the idea of moving to SQL Server 2008, which jtds has limited support for. Initial tests seem to indicate that jtds has better performance than the Microsoft supplied driver on 2005.

So my question is does anyone have any empirical evidence or any other good information otherwise indicating which jdbc driver is best suited for use with SQL Server 2005 and\or 2008?

Is jtds better? The driver supplied by Microsoft? Something else?

I've thought about profiling, but have doubts about whether this will really prove anything.

John Saunders
  • 160,644
  • 26
  • 247
  • 397
javamonkey79
  • 17,443
  • 36
  • 114
  • 172

2 Answers2

3

We had experience using the MSFT driver vs JTDS and we chose WITH NO DOUBTS the JTDS driver. Got less UNK problems, better performance and reliability. Not have any chart to demostrate, but our product is a POS for gas stations with more than 3k installations.

We are sql 2005, didn't tried in 2008.

Rodrigo Asensio
  • 2,760
  • 4
  • 26
  • 26
  • Something to be mindful of is that jTDS doesn't actually support XA (distributed) transactions. The official Microsoft driver does. For more information see http://jtds.svn.sourceforge.net/viewvc/jtds/branches/jTDS%201.2%20%28stable%29/README.XA?revision=1118&view=markup – NickTee Feb 20 '12 at 05:19
2

Is using the JDBC driver supplied by Microsoft an option?

Seems like it's kept up-to-date: supports JDBC 4.0, and MSSQL 2000/2005/2008.

matt b
  • 138,234
  • 66
  • 282
  • 345