> Out of curiousity, have you tried doing a plain INSERT instead of INSERT > OR REPLACE INTO? > Since you have no unique fields in your table, I'm not exactly sure how > or why you might get an > INSERT failure, but perhaps Sqlite is doing some sort of data comparison > on each insert.
We have one multi-field unique index, > CREATE UNIQUE INDEX [pkPrimary] ON [myTable] ([myKey], [NumOne]); Interestingly enough, on further tests (one developer forgot to create the index and was duplicating their data every time they ran a test) we discovered that the INSERT OR REPLACE INTO was not really much slower when it was doing it's job correctly He was getting 6 million records inserted into the DB in about 16 minutes. With the index added it dropped to about 18 but at least it was doing the right thing Thats still only about 2500 records a second, but getting much better!
