The unique index on DistinguishedName though is what gets used for that sub query of the insert, so most definitely keep that one index for the whole load. (The others can be left out until the end though)
Otherwise, as was mentioned, journal_mode = off, synchronous = off, a large cache_size, and running it all in 1 transaction are gonna be the things that help the most. You shouldn't need to do intermediate analyze runs, the defaults should use the correct indexes. -----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin Sent: Wednesday, May 17, 2017 12:05 PM To: SQLite mailing list Subject: Re: [sqlite] Bulk load strategy So if you never insert duplicates on AdObject(DistinguishedName), DROP that index. And definitely DROP all the others. Then do your users. The reCREATE the indexes. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
