The database version does not impact performance much. You can verify this yourself by converting your database files to the 3.3.5 format.
I'm guessing that you are seeing a difference in query performance between 3.2.1 and 3.3.5. Much code has changed between these two versions, including the algorithms for ORDER BY and GROUP BY. The "ANALYZE" statement was also introduced: http://www.sqlite.org/lang_analyze.html ANALYZE changes the table join order and helps determine index usage. If you use "CROSS JOIN" instead of commas in your FROM clause you can often simulate older SQLite3 table join behavior and timings, sometimes for the better. http://www.sqlite.org/cvstrac/wiki?p=QueryPlans You may also have to alter your queries to get acceptable performance. Some SQL command timings have improved in recent SQLite versions, while others have regressed. It depends on your specific database and usage. If you post your slow SQL statements and schema to the list I'm sure someone could give you a suggestion or two on how to speed it up. --- sandra <[EMAIL PROTECTED]> wrote: > We have recompiled several applications with new sqlite 3.3.5 library. > > We have observed that one of these application, which access intensively > (read-only) a large number (around 180) of old sqlite 3.2.1 db-files (4 > million records, 2GB, each) runs now much slower. > These files are updated sporadically by another application (also > recompiled with sqlite 3.3.5). > > Is there any performance degradation for a new, 3.3.5, application > accessing an old, 3.2.1, db-file versus an old application, 3.2.1, > accessing old, 3.2.1, db-files? > > Thanks, > Sandra Toloba __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
