<p>This debate has been going on in almost any SQL Server community for ages. there are good arguments for both sides and there is definitely not just one size fits all answer. It really depends on your individual situation and on many factors, such as number of users, avg. file size, update frequency, read/write ratio, disk-subsystem yadayadayada...</p>

<p>But as you mention SQLExpress probably the most important factor is the max database size limit and this is a very good reason to go for the filesystem approach. Anyway, this research paper might still be interesting for you: <a href="http://arxiv.org/ftp/cs/papers/0701/0701168.pdf" rel="nofollow noreferrer">To BLOB or Not To BLOB:
Large Object Storage in a Database or a Filesystem?</a></p>

<p>This paper used to be on the Microsoft Research site here: <a href="http://research.microsoft.com/apps/pubs/default.aspx?id=64525" rel="nofollow noreferrer">http://research.microsoft.com/apps/pubs/default.aspx?id=64525</a>, but that link doesn't work for me. SQL Server has come a long way since then. Quassnoi already mentioned FILSTREAM, for example.</p>
Which is a better method for storing images - folder or SQL Server as binary?
<p>I am planning the development of a photo gallery application for a client. I am developing the app in asp.net 3.5 and would like to develop it so that I can re-use the application across multiple platforms using various front-ends. Basically, I am wondering what are the dis-advantages and advantages of storing images in the database as binary files as opposed to simply storing the files in an application folder.</p>

<p>Any advice would be greatly appreciated! </p>

<p>Thanks,
Tristan</p>