>>>>Store paths to the images. Keep your database from massively bloating.
>>>>
>>>>Been there. Done that.
>>>
>>>Do you mean that with varbinary(max) the database is bloating? We're using it here and several of images with ntext / text fields as I found yesterday...
>>
>>Unless you are only going to store a few images, you can count on the database growing dramatically simply because the binary data is so much larger than any normal text records you are storing. Also, because each image adds a noticable increase in size, you will find the database has to physically grow more often, which can be painfully slow when it happens.
>
>Did you also implement physical paths for WEB app? It's probably a bit late for us to change the structure now...

I haven't had to store images for a web app - only windows based apps. That still is probably do-able, but it does add complications depending on where you can store files.

Storing images in the database makes coding much easier, but be warned that your database will suffer performance-wise if nothing else (assuming you store a lot of and/or large images).