Recently created a library module (ASP.Net and SQL Server 2005) where we store files inside the SQL DB. We now have several thousand files and the DB is around 25 gb. I think we are starting to see performance problems when trying to select files for download. Filed under 10 Mb seem to download fine, but over 10 MB we are having problems with. Was wondering if someone could point me to a good article that might talk about these kind of performance issues and what I might do to over come it.
-
-
Some disadvantages summed up here:
http://www.dbazine.com/sql/sql-articles/larsen13
Guess the simple answer is, if you are experiencing problems and you think it is retrieval time from SQL Server that is the biggest culprit it is time to think about storing just a pointer to the file rather than the content. Whatever the benefits perceived in storing binary in the db, performance wise using the file system is always going to be on another level IMO. -
Sometimes these SQLServer performance problems can be avoided by employing a compression technology in the Data Access Layer, or by cutting the data into managable chunks in the Data Access Layer before storage.
I believe the second strategy is the method used when they developed the TerraServer, which stores an enormous amount of large satellite images in SQLServer.Comment
Comment