Originally posted by Allen Thomas:
What do they mean "...in some situations..." batch updates would be efficient? Is there an example of where it would not be efficient to use it?
It is not efficient when database performance is not the bottleneck in the first place. It is not efficient when the individual updates in the batch take a long time compared to the time it takes to communicate with the database. It
is very efficient when you have a whole bunch of little updates that execute very quickly individually but together take a significant time.
I am using the standard JDBC-ODBC driver connecting to an access database. Did anyone have any problems that I will encounter?
In that case I'd be tempted to say: don't bother. If you run into performance problems then your #1 optimisation would be to move away from both Access and the JDBC-ODBC bridge.
- Peter