I would store the images at the file system with the metadata stored in the db. I find it easier for replication to a DR site and incremental backups. NON-Prod DB refreshes and restores would be simpler and faster. Gene Sais IT Dept. - Database/Unix Administrator Palm Beach County Clerk & Comptroller 205 North Dixie Highway, Room 4.2504 West Palm Beach, FL 33401 P: 561.355.3467 F: 561.355.2600 C: 561.329.4384 E: Gsais@xxxxxxxxxxxxxxxxxxxx ************************** FYI - this correspondence is public record (http://myfloridalegal.com/sun.nsf/manual/81A9D4BE9B3D71FF852566F300658372?OpenDocument). -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Chirco Sent: Tuesday, January 17, 2012 1:48 PM To: oracle-l@xxxxxxxxxxxxx Subject: storing blobs in database We are working on an application that will store images, well actualy pdf's in our database. We are debating on storing the blobs in our main production database or creating a separate database just for these images. We have applications running on our main production database that will need to pull these across to display. I am thinking a second database is the best idea since this database will get rather large very quickly and I don't want to slow down the backup of my main production database. Does anybody else do something similar to this and can provide your experiences. We are running 11.2.0.2 Enterprise Edition on Windows Server 20003 R2, soon to be 2008. Thanks. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l