On Tue, Mar 3, 2009 at 6:36 PM, Greg Palmer <gregorylpal...@netscape.net> wrote: > Trainor, Chris wrote: >> After running vacuum, sum is fast on the original table. However, >> running vacuum took a long time, so I'm not sure if that is a feasible >> solution. Is there any way to prevent fragmentation in the first place? >> If not for the whole database, then for a specific table? (e.g. is it >> possible to preallocate space for a table?) >> >> Thanks >> > I'm not an expert on SQLite but generally speaking fragmentation in a > database is usually a result of records being added and deleted. Are you > doing a lot of these and if so, can you change your algorithm to cut > down on this activity?
exactly the right approach. Even better, make your application do the vaccuming when your users are away, much like housekeeping in a hotel. > > Regards, > Greg > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Puneet Kishor http://www.punkish.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Carbon Model http://carbonmodel.org/ Open Source Geospatial Foundation http://www.osgeo.org/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
