InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 06:16:15 GMT20http://www.sqlservercentral.com/Forums/Topic1392478-391-1.aspxI would recommend the file system and store the path in the SQL Server. Ultimate flexibility and easiest to code.Tue, 04 Dec 2012 07:58:47 GMTDiverKashttp://www.sqlservercentral.com/Forums/Topic1392478-391-1.aspxThere are basically 3 ways to handle storing binaries with sql.1) Store the files on disc in a folder and then store the file name in sql. You basically just use sql as a way to track which file belongs to a given row in the table.2) Store the actual file in a varbinary(max) column. This can be a bit unwieldy as you get large numbers of files due to page and index fragmentation. You also have to be careful not to select that column with every day queries. I have done this in the past by having a table that holds nothing but the image, an identity and a foreign key.3) Filestream. Not sure this is what you want given the small size of the files you are working with. You read more about this option here. [url=http://msdn.microsoft.com/en-us/library/bb933993%28v=sql.105%29.aspx]http://msdn.microsoft.com/en-us/library/bb933993%28v=sql.105%29.aspx[/url]Tue, 04 Dec 2012 07:43:25 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1392478-391-1.aspxHelloour app is used for plant inspection. Each inspection file will have about 30 photos. We resize photos so each weights about 60 kWe evaluate 25 000 inspection file per year. So 45 gigs of photos in the database after one year and 90 gigs after two yearsHow to manage this efficiently in SQL Server? (performance...backup..etc)thanksMartinTue, 04 Dec 2012 07:26:14 GMTdubem1-878067