On Tue, Nov 23, 2010 at 10:13:34PM +0000, Paul Sanderson scratched on the wall: > I have a table with over 1 million rows and 20+ columns all of which > are indexed,
Unless you have an extremely diverse set of queries, that seems excessive. A compound index is unlikely to need so many columns, a series of single indexes won't get used unless you have many different query forms. > I reasonably regularly recreate the table with new data > and find that the indexing process takes about 30 minutes. Are there > any settings/tweaks that I can use to reduce the time required to > create the index? Making the cache size very very large (~100x the default) will help, but there are diminishing returns there. If possible, insert the data so that the primary index is pre-sorted. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
