Possible Duplicate:
Storing Images in DB - Yea or Nay?

Could it be faster and much more reliable to keep images within the file system or must i store these questions database?

Let us the images won't be any bigger than 200 Megabytes. The aim is fast, reliable access.

Generally, how does someone decide between storing files (e.g., images, Ebooks) within the file system or perhaps in the database?

Thanks!

Personal opinion: I Usually store images around the file system, and just store a filepath within the database. In lots of situations, databases are saved on fast (read: costly storage, 15k Revoltions per minute 450GBs, etc) storage. Images or any other files, typically could be saved on reduced (read: cheaper, bigger drives, 7.2k Revoltions per minute 2TBs, etc) storage.

I've found this to be the greatest, because it enables for that database to stay small in dimensions. Generally, databases store "data" well. They are able to search and retrieve small items of data fast. File Systems store "files" well, they're enhanced to locate and retrieve bigger items of data fast.

Clearly you will find tradeoffs to both approaches, there is not likely to be a 1-size fits all however, there might be some usecases where storing images within the database is really a positive thing, if they're all quite small, and also you don't anticipate very most of them, as well as your database is on a single storage medium as the file share, it most likely is sensible to decrease the pictures into the database.

Like a side note, SQL Server 2008R2 includes a FileStream area type, which could provide the very best of both mobile phone industry's, I haven't tried on the extender yet, and so i can't talk to how good it really works.

Store files/images within the database should you require following:

  • Access Control
  • Versioning
  • Checkin/Take a look at
  • Searching according to metadata

That's been the style of major Content management systems like SharePoint continues to be.

However, in case your content is a lot more static and never likely to change with time , you are able to opt for files ystem and let optimizations/cache on the internet server.

Using the database approach, you simply have one factor for connecting to. In case your customers are distributed, that could be simpler. Observe that when the images aren't utilized too often, the efficiency issues may not matter.

To begin with you must understand that in databases, you cannot store files larger than i believe 8 megabytes, leavinig that, and so i think 's better to store files within the system, and small images within the database