Hy
using old JBDC Bridge for MSAccess is faster than HXTT_Access.
I make some test and on same amount of data I need 1,30 minutes using JDBCBridge with HXTTAccess more then 7 minutes.
Is there an parameter to set ?
bye
|
It's possibly resulted by query sql, which hasn't utilzied index.
What's your jdbc url and main sql?
|
Sorry what do you mean with
"It's possibly resulted by query sql, which hasn't utilzied index.
What's your jdbc url and main sql? "
My program is the same I onyl change the URL when connecting to the MDB file.
To connect to ACCESS MDB with JAVA JDBC is
jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=c:/temp/appoggio.mdb;}
To connect to ACCESS MDB with HXTTACCESS is
jdbc:access:///c:/temp/appoggio.mdb?delayedClose=0;lockType=ACCESS
To write in the MDB FILES I get 7000 records from my data and with INSERT INTO command I write data into MDB file.
Using JAVA JDBC is faster than HXTTACCESS .
So the only difference it that I use the JAVA JDBC or the HXTTACCESS URL rest of my program is the same for extract data to write into the MDB file.
Bye
|
Try to remove delayedClose=0;lockType=ACCESS
Your test code should being reload total file for every insert operation, since there's only 7000 records.
|
If you read old tickets I have to use "delayedClose=0;lockType=ACCESS " because of corruption problems.
My prg doesn't load file for every insert operation...
Bye
|
In my memory, corruption problem:
2019-09-18 fix a seldom index format compatible bug for level information of root node when it downgrade from index node to leaf node. It does not influence data, but MS Access will think it's incorrect.
So that you needn't concurrent lock check.
|
|
Ok I'll try to change connection without delayedClose=0;lockType=ACCESS...I'll let you know.
|
Main
webmaster@hxtt.com