InfRes
unread,Nov 6, 2009, 5:58:20 PM11/6/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting
Cerebrus,
Just wondering your reasoning for being against storing images in the
DB?
It makes sense in this senario, as profile images are likely to be
small
Also in this case the image will have plenty of metadata for it in the
database
and storing them together makes sense.
While these are 'public profile' images, another pro of storing images
in the db
is that they are subject to the same security as the rest of the data
in the application.
Sql Server Filestream type is mentioned here too, and while this
offers the best of both worlds, it does also mean
allowing the database run os tasks which may or may not be
desireable...
Coming from an enterprise content management background, where this is
common
(granted the enterprise content databases are optimised for the bigger
files)
I'd be interested to hear your counter arguments.