Large bulk inserts with more than one index (implicit or explicit) is not SQLite's strong suit.
If you search the mailing list archives you'll find a few suggestions: - "BEGIN EXCLUSIVE" (or is it "BEGIN IMMEDIATE"?) on the database file and then copy the file over - fastest way or - increasing cache sizes - pre-sorting the data in index order prior to bulk insert - creating the other indexes after all the data is inserted If you do not require a live backup you could use the copy trick and augment that with a daily archive via sqlite3 file.db .dump | gzip etc... in case the database file becomes corrupted. --- [EMAIL PROTECTED] wrote: > I am trying to put in place a simple replication process to copy a database > from one machine to > an other. ... > My question is: > > is there a way to do a select or a .dump so that when inserting the data on > the other end, > things will be faster? Or maybe there are some pragmas I can use that would > improve performance? ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
