We are using the sun.jdbc.odbc.JdbcOdbcDriver and this is causing severe performance issues. Can anyone suggest a quality database driver?
The best thing to do would be to avoid a JDBC-ODBC bridge altogether. In Sun’s words, the Sun JDBC-ODBC Bridge is only ‘appropriate for experimental use and for situations in which no other driver is available’. They also state ‘The JDBC-ODBC Bridge should be considered a transitional solution.’ These statements are as recent as JDK 1.4.1. Basically the bridge is provided just to get you going. It shouldn’t be used for “real” stuff. One of the main issues is that it isn’t thread-safe.
If you can, use the JDBC driver from the database vendor. Lacking that, BEA and DataDirect have a good set of available drivers. If you really want to use a bridge, take a look at http://www.easysoft.com/products/9999/documentation.phtml?product=2003
http://industry.java.sun.com/products/jdbc/drivers is a good resource for information.
You didn’t mention which database you are using. MS SQL 2000 supports a Microsoft Type 4 which I find really good.
One of the fastest Native Drivers is JTurbo. I know several companies who use this with much success.
Here is a link of all JDBC drivers from SUN:
Thank you guys for your suggestions. We are using SQL Server 2000 as the database. I have downloaded the driver for SQL server from windows.
I am using webMethods Enterprise JDBC adapter to connect to MS SQL Server 2000 via the MS jdbc type 4 driver.
I have a problem. When working in Enterprise Integrator, I can’t see the Select (one record) operation. The only Select operation available is the multi-output type.
The JDBC adapter docco says there is a Select (one record) operation, so where has it gone to?
Is this normal? Is there a way to fix it?
We are using Microsoft’s own pure Java driver in production
with zero problems and good performance: