> -----Original Message----- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On > Behalf Of Simon Slavin > Sent: Wednesday, May 17, 2017 2:02 PM > To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Subject: Re: [sqlite] Bulk load strategy > I forgot: once you’ve remade the indexes run ANALYZE. That’s the only time > you need to do it. At that time you have typical data in the tables and > SQLite > will be able to gather all the data it needs to figure out good strategies.
Thanks for all the assistance guys, its working within reasonable limits on the hardware given. The unique constraint on a distinguished name is more about data integrity. I am associating data against that value and it doesn't make sense to have more than one. So if an "add" comes along unexpectedly (instead of an "update"), the best way to know something is awry is for everything to turn pear shaped. Kinda makes it hard for bugs to go unnoticed:) Much appreciated everyone, jlc _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
