asp.net storing images in the database versus the file system
Posted on 2014-10-27
I am updating an old asp classic website. The old website stores the images on the file system. I am updating to asp.net where I upload and store my images in the database.
I've read some pros and cons on storing in the database versus the file system; but it's not really clear what the final recommendation is. Can anyone just tell me in a nutshell what you believe the pros and cons are?
1. I will need to import my file system images into my database. Will this be possible to read the images from the hard drive and then put them into the database? (If yes, I will ask a new question on how to do that.)
2. I will be using a cloud server and when it needs to spin up a new copy of the database for replication, will having the images in the database cause any problems?
3. Will my costs be greater? I will be using Rackspace cloud, so if I just have a file sharing server versus storing images in the database, what might be the difference in storage costs? Any ideas?
4. The structure of my field for storing the image is this, any suggestions on something else? I am using VS2008 now for testing, but will up to 2012 when I move to the host.
[UserProfileImageContent] [varbinary](max) NULL,