On Oct 27, 2008, at 7:34 AM, MikeW wrote: > Mohit Sindhwani <[EMAIL PROTECTED]> writes: > >> >> Cory Nelson wrote: >>> vacuum shrinks the database size by removing empty pages. sqlite >>> will >>> normally reuse empty pages - so vacuum is only useful if you don't >>> plan to insert anything else, otherwise it will be slower. >>> >> >> Thanks Cory! That clears a major worry (regarding the speed of >> vacuuming a large database with a large number of records deleted) >> in my >> mind. Temporarily, letting the database take up extra space is not a >> worry, so we'll just leave it in the records deleted state and let >> SQLite reuse the memory as it goes along. >> >> Best regards >> Mohit. > > Though if your db has reached a steady-state size you might consider > running a VACUUM just *before* deleting the records, to avoid peaks > persisting ... and even then (say) every *other* week. > Just a thought ! >
VACUUM also defragments a database file which sometimes helps subsequent operations to run faster. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
