How about Alfresco as a C/DMS? (http://www.alfresco.com/) Our CEO read an article about Boise Cascade using this model and thought it would scale well for us.
There is also this http://www.mysql.com/news-and-events/web-seminars/mysql-alfresco.php Which I didn't know about (or necessarily care ;-) on March 9th. Right now, some of our DBs are about 35-40Gb, of which half or slightly more consists of archive blobs. This archive feature is increasingly popular and so we're looking to move it out of the main database(s) and onto a separate server. Tim -----Original Message----- From: Daniel Kasak [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 18, 2006 11:35 PM To: Tim Lucia Cc: mysql@lists.mysql.com Subject: Re: Document / Image (Blob) archival -- Best Practices Tim Lucia wrote: > Hi all, > > > I am considering moving some archival records which largely consist of blobs > (PDF Image files) out of an Oracle DB and onto MySQL. Has anyone done this > (not necessarily the Oracle part) who can relate their experience(s)? I can > go with MyISAM or archive storage engine, from the looks of it. This is not > transactional data, although eventually some reporting may be required > (although since the blob data are things like fax archival documents, I'm > not sure what can be reported.) > > > > Another possible storage model would be to use MySQL as the index but put > the blobs (.PDFs) into some document management system. If you've done > anything like this, I'd like to hear about it as well. > I've done a couple of file-based systems. Briefly: - separate filename into the actual name and the extension - insert details into MySQL table - fetch primary key - figure out where to store document - *copy* the document there, with a new filename: PRIMARY_KEY.arch ( replace PRIMARY_KEY ) - test that it's there - delete original I rename the file to make sure I've got no filename clashes. It also stops people from editing archived documents by snooping around your network shares ( they don't know how to open a .arch file ). I also have a limit of 100 files per folder. If you put too many files in 1 folder, directory listing slows down a LOT. I know others have had great success with storing blobs in MySQL tables, but I really don't think that's the way to go. Maybe I'm just paranoid, but storing things as real files seems safer to me. I've considered writing an open-source document archiving system, using a gtk2-perl GUI and a MySQL backend. It would be trivial to do - as I said, I've done a number of special-purpose ones already. If other people show an interest I'll have one up over the next couple of days / weeks. It will of course be cross-platform. Dan -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
