in reply to Is it a good idea to store images in a RDBMS?

I would not recommend this proceedure for the following reasons. 1. I was fighting with this same issue using VB6 through an Access 97 database. (which should have done the job well) I crunched the size of the images to thumbnail size prior to inserting into the database yet the database was huge, 5.6 megs with only 3 text fields and the one image field. (Long binary data) I had only 500 records. DATABASE to large. 2. The main issue, images stored in databases are far too large. You never get the value expected, a 4k image is stored as 12-18k etc. With my project I ended up leaving the images out of the database and just put them in directory locations and called them through my code. I am much sronger in Perl than VisualBasic and if the situation required Perl I would NEVER put images in a RDBMS database. In fact I don't care how it is layed out, the language, or otherwise images in databases are just a nightmare. Just my 2 cents
  • Comment on Re: Is it a good idea to store images in a RDBMS?