Sent from my iPod On Apr 11, 2009, at 10:40, Tito Ciuro <tci...@mac.com> wrote:
> Hello, > > I'm sure this question has been asked before, but I haven't been able > to find it in the archives: when does it make sense to vacuum? If an > application which deals with a large database vacuums say, on > termination, it may take a long time to process them and not gain much > from that operation. I understand that vacuum is needed when lots of > "holes" are left behind after many objects (table, index, or trigger) > have been removed from the database. > > The question is: what is the threshold I'm looking for? Is there a > formula I can apply that would hint to me when this op would be > beneficial? I can't offer a formula, but I suggest making it an option for the users of the software, with sufficient warning that it could take some time, as well as a Cancel button. Another thing you could do is to schedule the vacuum for a time when you know the software won't be in use -- for example, those of us who write software for K-12 schools can safely schedule operations like this for midnight on weekends. :-) _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
