I don’t mean to hijack the thread, but unless your database is fairly small… storing binary data such as pictures, files, etc. directly in the database will greatly reduce its performance, and significantly increase its size (making backups, etc. a nightmare). If you haven’t yet, consider storing the data in the filesystem and just store path references within the database. This way, the database stays small, becomes less fragmented (you let the filing system handle the fragmentation issues for the binary files), and everything stays more efficient and smooth.
EDIT: This is unless your SQL database recognizes the FILESTREAM type, which if stored that way instead of a BLOB, will handle everything for you as above (which is probably the safest way to do it, as it should minimize broken links from data that isn’t sync’d should a restore need to be done).