Ok, some thoughts about why you shouldn't put them in the DB. I will grant you this is a bit old school in thinking but it is something to consider.

Why put something in a database

-- You need to search on it

-- You need to really control access and NTFS security is too big of a pain

-- You need to control multiple people accessing a piece of data and modifing it

So why not put something in a database.

You don't have to worry about the data changing, how it is accessed or searching on it. (And depending on the searching requirement there may be better tools than SQL Server).

So if you BLOBS are spreadsheets that change every week put them in the database. If the BLOBS are scaned documents don't bother.

But you may say why not just put everything in the DB.

Also in the grander scheme of things database storage is more expensive: Management cots, backup costs, licencing costs, hardware costs, etc. Also why have the SQL Server engine spend cycles dealing with documents when the engine adds no value to the process.

In Summary:

If you have static BLOB documents & Objects (for example scaned documents) don't bother putting them in the database.