Been talking to a fellow about this very topic over the past few weeks....
He runs a Web photography biz and suggests that there are several issues.
First, whether the images are "archival", that is, not really changing
once inserted, or "active", that is, where the image may change
frequently.
Second, whether your database can do incremental backups. If you have a
primarily archive oriented database and can't do incremental backups,
you will be backing up the same data over and over, and the backups can
get quite lengthy if the database gets large.
By just using pointers, the database size is minimized, and you can
backup the images separately a single time. Your database backup time
is minimized in this case. If your database can do incremental backups,
the problem is lessened, but if the number of images gets very large, I
think it can still start to impact database performance.
Just another $0.02.
Whil
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
