Jim Lawrence (AccessD)
accessd at shaw.ca
Tue Nov 30 17:32:34 CST 2004
Hi Steve: Have you had a chance to test the performanace rates, comparing the standard storing method (outside the SQL) and new ADO.Stream method. I would be interested to hear the results from a large 'imbedded' implementation. Just one question: Why were the files all convereted to GIF format instead of maybe JPG? Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Steven W. Erbach Sent: Tuesday, November 30, 2004 11:05 AM To: 'dba-sqlserver at databaseadvisors.com' Subject: [dba-SQLServer] Graphics in SQL Server table Dear Group, Even though the standard advice for storing graphics on a web server is to store them in the file system, I've decided to store graphics in tables. I've used the ADO Stream object to read GIFs from disk and write them into an Image field. I found that the original images (over 4,000 GIFs) averaged 53.6KB each. When they've been written into the SQL Server tables the amount of table "space" allocated for each image stored averages 63.2KB. So there's about 10K of "overhead" (about 18%) for each image. Not bad. Getting the images out of the original Access database was a bit of a chore, though. Fortunately IrfanView allows command line options to paste an image into the window and convert the image to a GIF. I was able to cycle through all the images in relatively short order by copying to the Windows clipboard and pasting and saving with IrfanView. Steve Erbach Neenah, WI sweblog1.blogspot.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com