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? Thanks in advance, -- Tito _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
