One of the advantages of storing image data in a database is that backups of the database are all-inclusive. You don't need to have a backup of the file system that is coincidental at a point in time with the database backup in order to restore the data.
I have an application where the images are generated in a factory from an inline inspection tool. These images need to be kept in context with the history records from the lots in progress. If I were to store the images outside the database, then data integrity would be suspect.
As it stands now, I can restore a database backup from 5 years ago, and I know that I have the lot history data, all measurement data, and the supporting images that went with the inspections, all in one place, all in one convenient restored database.
Trying to do this with multiple backups of both database files and RMS files always results in something being missing.
-t