BLOBS in the database

Am I doing something horribly wrong here? I have around 100 JPEGs I want stored within the database (ie, as a BLOB, not merely a BFILE). Not one of these pictures is larger than around 80K. I've just loaded 50 of them, and I'm up to 106 *MEGS* of storage.

I haven't done much work with BLOBS before, and I expected a bit of fluffiness with these things, but not quite so fluffy that I need to buy a new hard disk to complete the project, thanks very much!

8.1.7 on W2K, graphics are being loaded via an OLE Linked object frame in Access, via ODBC. I'm using an 8K block.

I've seen this same behaviour on, >cough<, SQL Server 2000, so I suspect it's an intrinsic feature of the way these things are stored internally, but I'm surprised if so that it appears so *very* inefficient. Any suggestions for different ways to go about this, gratefully received. The thing is, after this I'm scaling up to around 8000 graphics, some rather larger, and the whole point is that I do not want 8000 separate JPEG files floating around on my hard disk.

Where are the good developers when you need one, huh??!

Regards
HJR

--


=============================!!=============================

The views expressed are my own only, and definitely NOT those of Oracle
Corporation


=============================!!=============================