8 ms·

Yay... Isnt everyone using jTDS anyway because it is reliably faster? https://social.msdn.microsoft.com/Forums/en-US/36e7b9cf-5bc5-445d-874c-1d6f8e819b63/ms-j

by ysleepy 10y ago

Yay... Isnt everyone using jTDS anyway because it is reliably faster? https://social.msdn.microsoft.com/Forums/en-US/36e7b9cf-5bc5-445d-874c-1d6f8e819b63/ms-jdbc-driver-performance-observations-versus-jtds?forum=sqldataaccess https://social.msdn.microsoft.com/Forums/en-US/36e7b9cf-5bc5... http://stackoverflow.com/questions/7848213/why-is-jtds-faster-than-microsoft-jdbc-driver http://stackoverflow.com/questions/7848213/why-is-jtds-faste... Edit: seems like they fixed their abysmal performance after 5years in jan 2016; see stackoverflow comment.

starnixgod 10y ago
The jTDS project is dying, there has not been a new release in over 3 years despite some pretty significant bugs. https://sourceforge.net/p/jtds/discussion/129584/thread/050f9892/ https://sourceforge.net/p/jtds/discussion/129584/thread/050f...
- ysleepy 10y ago
  Yeah, maybe we'll switch as well now. But I just cant stand the loving hype for MS here. They gave out such horrible and dog slow drivers to their paying customers that people reverse engineered the protocol and wrote their own. And it still performs very well. Now that MS publishes this codebase (which should have been standard, or at least best, practice), they get showered with love. Like an abusive relationship where one is happy and extatic if the abuser is reasonably nice for a day.
  - jarjoura 10y ago
    You don't need to reverse engineer the protocol. TDS is an open spec on their website.
    - ysleepy 10y ago
      SQL Server TDS spec was published in 2008, when jTDS was in version 1.2 and already feature complete and stable.
  - needusername 10y ago
    I just had a quick look at the code and the code quality leaves a lot to be desired. If internal quality is an indicator for external quality there is indeed a lot of room for improvement left. While Microsoft claims the new driver is fully JDBC 4.1 compliant key JDBC 4.1 methods throw SQLFeatureNotSupportedException and the code is littered with comments // The driver currently does not implement JDDBC 4.1 APIs
olavgg 10y ago
Recently I had an issue with connection timeouts in my connection pool when using the jTDS driver to connect to the Azure SQL Server service. When I switched to Microsofts updated JDBC driver, that problem was solved immediately.
elchief 10y ago
jTDS doesn't seem to support figuring out parameter types from a statement, but the MS one does, so we use that instead
batterseapower 10y ago
As if the fact that jTDS is mostly unmaintained wasn't enough reason not to use it, the MS driver supports several extra useful features e.g. bulk insert and availability groups (for AlwaysOn)

by ysleepy 10y ago

starnixgod 10y ago

The jTDS project is dying, there has not been a new release in over 3 years despite some pretty significant bugs. https://sourceforge.net/p/jtds/discussion/129584/thread/050f9892/ https://sourceforge.net/p/jtds/discussion/129584/thread/050f...

ysleepy 10y ago
Yeah, maybe we'll switch as well now. But I just cant stand the loving hype for MS here. They gave out such horrible and dog slow drivers to their paying customers that people reverse engineered the protocol and wrote their own. And it still performs very well. Now that MS publishes this codebase (which should have been standard, or at least best, practice), they get showered with love. Like an abusive relationship where one is happy and extatic if the abuser is reasonably nice for a day.
- jarjoura 10y ago
  You don't need to reverse engineer the protocol. TDS is an open spec on their website.
  - ysleepy 10y ago
    SQL Server TDS spec was published in 2008, when jTDS was in version 1.2 and already feature complete and stable.
- needusername 10y ago
  I just had a quick look at the code and the code quality leaves a lot to be desired. If internal quality is an indicator for external quality there is indeed a lot of room for improvement left. While Microsoft claims the new driver is fully JDBC 4.1 compliant key JDBC 4.1 methods throw SQLFeatureNotSupportedException and the code is littered with comments // The driver currently does not implement JDDBC 4.1 APIs

olavgg 10y ago

Recently I had an issue with connection timeouts in my connection pool when using the jTDS driver to connect to the Azure SQL Server service. When I switched to Microsofts updated JDBC driver, that problem was solved immediately.

elchief 10y ago

jTDS doesn't seem to support figuring out parameter types from a statement, but the MS one does, so we use that instead

batterseapower 10y ago

As if the fact that jTDS is mostly unmaintained wasn't enough reason not to use it, the MS driver supports several extra useful features e.g. bulk insert and availability groups (for AlwaysOn)