Hi,
General consideration:
A. Run insert in "bulk fashion":
BEGIN
INSERT INTO /* ~10000 - 2000 (or more) inserts line*/
COMMIT
B. If index have complex clause please don't create index until you finish
data upload in tables.
Good look
----- Original Message -----
From: "J. R. Westmoreland" <j...@jrw.org>
To: "'General Discussion of SQLite Database'" <sqlite-users@sqlite.org>
Sent: Friday, May 08, 2009 4:45 PM
Subject: [sqlite] Database creation and inserts speedup
>I have a program that creates a database with a number of tables and a few
> indexes.
>
> I'm just inserting in this program and not doing any lookups.
>
> I create the indexes after all records have been inserted.
>
> The input for the database is a LARGE number of records.
>
>
>
> The data is mapping data for the U.S. and therefore contains millions of
> entries.
>
> The current run is taking about three days for the entire U.S. to
> complete.
>
> A single state, say California, is taking several hours.
>
>
>
> Any suggestions on speed-ups?
>
>
>
> Granted this only has to be done once but if there is a failure along the
> line it could be bad. <smile>
>
>
>
> Thanks,
>
> J. R.
>
>
>
>
>
>
>
> --------------------
>
> J. R. Westmoreland
>
> E-mail: j...@jrw.org
>
> Twitter: GeneralJR
>
>
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
