On Mon, Jan 19, 2009 at 06:22:33PM +0100, vlema...@ausy.org wrote: > Hello, > > We need to produce copies of our databases for archive. > It is a requirement that the size of those copies being as small as > possible, without having to perform an external compression. > vacuum doesn't seem to perform a compression (it works on fragmented > data), is there any other way to do that ?
If you're taking snapshots of your databases while live, be careful not to just copy the database files, as changes may be occurring in the database while you're taking a copy, leaving you with an inconsistent file. In which case, you'll probably want to script some sort of archiving, using perhaps the sqlite shell .dump command to take a text dump of the database (which will lock it correctly) or to start an exclusive transaction while you copy the raw database file, before a rollback to unlock the raw database once you've finished copying. Either way, by scripting it, you'll have the opportunity to also compress the file (dump or raw). Having an arbitrary no compress policy without good justification seems like a poor policy to implement. > > Vincent > Christian _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
