asked on

Sun JDBC-ODBC driver to Microsoft Access DB slow in certain circumstances

Hi,

My Java 1.3 application connects to a local Microsoft Access DB (200MB+) using Sun's JDBC-ODBC driver. When running queries, it's performance is acceptable (a few seconds) when the application is running on Microsoft 98 or 2000, and completely unacceptable on Microsoft XP Pro or Home (a few minutes). I changed to another driver and it's performance is now the same for 98, 2000 and XP (a few seconds).

My question:
1. Why the discrepancy? Why would the driver work well on some operating systems and not on another? It's exactly the same JRE, same application, same data. Is there anything (for example, a patch) environmental that I can change on the XP machines that will fix the problem?

2. If there's nothing that can be done to enhance the Sun driver's performance on XP, are there any good free drivers? The application is installed all over the country, and so replacing the driver will not make business sense.

Thanks!

Pam.

mmuruganandam

The ODBC itself is too slow just because of the reason that it is not multi-threaded. So when there is many calls at a time, each call will be processed one by one.

I don't think you have drivers for that. Still search out you may find one.

TimYates

I'm not sure if the JTDS driver works with Access or not...

It works with SQL Server...and MAYBE Access...

http://jtds.sourceforge.net/

TimYates

Hmmm...reading the FAQ, it doesn't look like it does....sorry...

mmuruganandam

It supports only for

JDBC 2.1 driver for the Microsoft SQL Server series (6.5, 7.x and 2000) and Sybase 10.

Mayank S

You might try to use Connection pooling, if that's possible. I'm not sure if there is a driver for Access that allows pooling, but you can spend some time reading: http://webdevelopersjournal.com/columns/connection_pool.html

CEHJ

Proabably easier to get a proper, free database

Mayank S

Pay attention to the important word: >> *proper*

;-)

ASKER CERTIFIED SOLUTION

TimYates

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CEHJ

Not forgetting HSQL, depending on the scale of the application being quite small

http://hsqldb.sourceforge.net/

Tommy Braas

I would recommend in the short term to basically create the connections you need, and keep them alive. Creating new connections to a database is quite expensive (read takes time). In one of my applications I use a connection object that I keep around for each DAO, although that approach doesn't scale well to many DAOs, it works for my case with 8 DAOs. It might work in your case as well.