Leo, The jTDS driver has the same issues as the MS (DD?) driver concerning
the mapping of JDBC connections to physical database connections when used
in static mode. At least the MS driver offers the use of the cursor mode
which solves these issues but is much slower.

Note that the connection mapping is killing for locking control,
transactions and temporary table handling. It is all cuased by the idiotic
SQLServer limitation of a single active (static) cursor on a database
connection. The JDBC spec specifies no such limit so drivers tend to map one
JDBC Connection instance to more than one physical database connections
leading to the said problems.

I know for sure that jTDS still has these issues. If you can work around
them it is a very good JDBC driver.

Regards,

Silvio Bierman

Judging from the comments of others in this group, it is the MS drivers
which aren't production-ready. I used jTDS in one relatively modest app for
a large Australian bank. Not many users, low transaction volumes. But the
thing is that it never missed a beat. And others have reported similar
experiences. I have never heard a good word about the MS drivers. But then,
MS have little reason to give more than lip service to Java connectivity.

Try searching Google Groups for past articles on this subject, as I did when
I needed a driver. It'd been thoroughly discussed.

Luke