We're facing an issue with database size, and it brought to mind some possible feature enhancements that have been discussed previously, and I'd appreciate some clarification/updates/suggestions.
Currently all file attachments (other than, optionally, image attachments) are stored in blobs in the database. I'd like to know if there is any progress or intent to optionally use file-storage. Database space is quite a bit more expensive than filesystem space.. If I have to move my database off to a NAS, then all my database queries are hitting the network, while the majority of the queried info can be contained within 50m or even a gig, while my attachments take up many gigs of blob space.
I also understand that there is no compression of these attachments. Office2007 files are already compressed, but a routine process that compresses old versions of files could save space without a performance impact.
I recently read a post about limiting number of versions stored. This could be a valuable space saver, as old versions of many documents are unimportant. We have a great example here of a spreadsheet that is updated several times per day over the past couple weeks. We're already up to 70 versions. I can see my users doing something like this routinely for months or years, and ending up with thousands of versions. I'd like the ability to set a default 'number of versions to keep', and then users could, when viewing 'manage versions', select larger numbers of versions to keep from a dropdown box. An additional nicety would be to allow users to flag version to store indefinitely, from that same screen.
Is there a mechanism to archive old "spaces" (projects?) out of the database? My back-of-napkin brainstorming was to have an archive process that resulted in dumping a compressed single file "image" of a space into an archival location. In my case, this would conveniently be an NFS mount that has a more relaxed backup schedule. In the future, if I wanted to access one of those spaces, I could browse the 'archived spaces' table in the admin console, and re-invoke that space somewhere in my space tree. It would be re-invoked 'in archive' mode, where everything is locked, and read-only, with clear labeling that is it an archive of a certain space from this certain date. My only option now is to delete the space.. losing the content.