On 5 Jul 2012, at 9:34am, _ph_ <hauptma...@yahoo.com> wrote: > I already read your previous replies, but to revisit my scenaro: > > - My OS is "sensitive to fragmentation" > - We are running with auto-vacuum enabled, so the freelist_count is usually > small (not a good indicator)
Ah. If you're always running auto-vacuum, then I don't think explicitly issuing VACUUM is going to be useful at all. Don't bother. > but fragmentation supposedly gets worse Fragmentation of the database file on disk is something that SQLite can't control, so you are down to the various defragmentation facilities (including the one built into Windows) to solve that. > -We use sqlite as application data format, a typical user has dozens of > files. > This makes "During a support call" is not an option Okay. > So for me from reading documentation and this list, there's an "omnious > cloud of defragmentation looming" - wthout much data how bad it is or can > be. You could use the shell tool to turn the database file into SQL commands, and then back into a new database file on disk. This will both defragment the file, and make sure it's not using unneeded space. Of course, it's a very slow process, and most people will use it only when they think their database file is corrupt. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
