Re: [sqlite] VACUUM and large indices: best practice?

On Fri, Aug 30, 2013 at 3:52 PM, Simon Slavin wrote: > Great question. If all you are doing is writing (never any UPDATE or > DELETE FROM or DROP) then VACUUM won't save any space in your database > file. It would defragment your database and might thereby increase speed

Re: [sqlite] VACUUM and large indices: best practice?

Hi, Im Auftrag von uncle.f > Hello all, > > I have a process that runs 24/7 and permanently inserts data into an SQLite > database: > > 1) Create new database at midnight, keep it open for writing for the next > 24 hours > 2) There are no deletions and not even reads during the database

Re: [sqlite] VACUUM and large indices: best practice?

On 30 Aug 2013, at 9:32pm, uncle.f wrote: > I thought of several options: > > 1) VACUUM before creating indices, then create indices, then move database > off to storage > 2) Create indices, then VACUUM, then move off to storage > 3) Create indices, move to storage, VACUUM

[sqlite] VACUUM and large indices: best practice?

Hello all, I have a process that runs 24/7 and permanently inserts data into an SQLite database: 1) Create new database at midnight, keep it open for writing for the next 24 hours 2) There are no deletions and not even reads during the database creation 3) I use only bulk inserts wrapped in a