Hi,
With storage becoming cheaper and cheaper by the day, the only consideration I would give
is whether it would be detrimental for the Database to store any large files. If not,
then I would very much have the DB as the single place of storage.
IMHO, storing attachments separately in file systems and just storing a reference to them
in the DB, is the old-way of thinking. I guess in those times, the performance and the
storage required by DB were greater concerns. And file systems (I think) were faster than
DB in retrieving files.
Today, there are thoughts of atleast conceptually merging the DB and the File System
(Microsoft's WinFS) and the modern DBs don't seem to bother about large chunks of data
stored in them. That being the case, in my opinion, we would rather have everything in
the DB and the configuration / settings alone separately in a Config file - which is
already being done by Eventum.
I have had enough of "Dangling References" and I really like the Eventum way as it avoids
many administrative headaches. I have implemented a Grievance Cell application by
customizing Eventum and deployed it on an old Dell PowerEdge server powered by PIII (I
think). Around 20,000 people have aired their grievances with a significant number BMP /
JPEG attachments (each around 2MB on an average). And till now (for 6 months) there has
not been any issue. The only addition we made was to put a fast SCSI RAID disk for
300GB.
I think MySQL is a doing a very good job in handling such large chunks. I believe that
other modern DBs (like PostgresQL) should also do the same.
Thanks and rgds,
Watson
-----Original Message-----
From: Bryan.Alsdorf@stripped [mailto:Bryan.Alsdorf@stripped]
Sent: Thursday, September 11, 2008 9:32 PM
To: German Pizarro
Cc: Anders Klarström; eventum-users@stripped
Subject: Re: SV: File Uploads larger than 1mb
Hi,
German Pizarro wrote:
> For small sizes, files saved into the database are OK, but for filesbigger than 1MB,
>
> wouldn't it be better to save them in the file system (blocked direct access via
> http, but accesed via php proxy for authentication/authorization)?
This can be a hotly debated topic, I have gone back and forth on it many times. The
problem I have with storing things on the filesystem is you then have an additional set of
data you have to back up. I like now that everything is in the database and I can backup,
replicate, etc all in one spot. The con is the database grows considerably.
Best Regards,
--
Bryan Alsdorf, MySQL Support Manager, Systems
MySQL @ Sun Microsystems, Inc., http://www.sun.com/mysql/
--
Eventum Users Mailing List
For list archives: http://lists.mysql.com/eventum-users
To unsubscribe: http://lists.mysql.com/eventum-users?unsub=1
Important notice:This e-mail and any attachment thereto contains corporate proprietary
information. If you have received it by mistake, please notify us immediately by reply
e-mail and delete this e-mail and its attachments from your system. Thank You.
