0

I'm planning to develop web app. to store real estate information.

Tech. details: MSSQL, NHIBERNATE ORM, C#, ASP.NET MVC3

Property will have some properties like Created, Updated, Id, Name, ... and IList<Photo> Photos. So here will have one to many relations, one property can have many photos. On the other side on Photo entity have reference to Property object and ImageData and ImageMimeType to store photos in db.

This solution is recommended in apress book mvc3 pro to store images, but I'm wondering what will happen when these database become huge because of images that are stored inside. Any thought are helpful.

Which approach do you use? Db or file path on the server? Any thoughts, links are helpful. thanks

Grunf
  • 482
  • 8
  • 21
  • possible duplicate of http://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay – sinelaw Apr 27 '12 at 20:54
  • 1
    storing image data in a server is rarely recommended. It usually results in large, unwieldy backups that are difficult to maintain and store and performance problems as well. – Jeremy Holovacs Apr 27 '12 at 20:56

1 Answers1

1

As stated in this article ....

Storing URL is much easier to ADD, EDIT, DELETE, Database size also reduces, as oppose to store image in binary format.

naim shaikh
  • 1,103
  • 2
  • 9
  • 20