I've been comparing three .Net providers along with the JET OLEDB provider. I have the same data in an MDB and also an Sqlite db.
The providers I've used so far, all on Windows, are: - The Mono Sqlite client http://www.go-mono.com - The AGS Sqlite provider http://www.ag-software.com/sqlite.aspx - The SQLite.Net project here http://sourceforge.net/projects/adodotnetsqlite/ The database is not huge. For the example query, there are two tables joined using a subquery. Table A has 11,000 rows; Table B has 200,000 rows. The performance of the three .Net providers is near-identical. On the first run, with the system restarted to eliminate any caching by the file system, it takes about 4 seconds to execute the query and fill a datagrid with the results. On subsequent runs it takes about 0.25 seconds, showing the dramatic effect of the caching. The JET provider is an interesting case. The first run takes about 9 seconds. However, subsequent runs are about 0.15 seconds. Aside from indexing, I've not made any special effort to optimize. I know how difficult it is to do performance tests, and I don't pretend these notes have any authority. They are just offered as a point of general interest. Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
