Analysis Document

Job: There are two requests that have come in: 1) Move all files into a database. ( I believe the mssql FILESTREAM data type might be the way to go due to the amount of files/file sizes and performance issues). 2) Move database storage onto a device that can handle many TB. Background: Database: MSSQL 2008 R2 A current project stores user documents on a file system. Everything currently everything (file system, webserver and database) is on a single virtual box. The average file sizes are from 100kb - 30mb. The total amount of files are 750gb, and growing quickly. (Estimated at 1TB by end of year). This will soon approach standard virtual disk size. PROJECT REQUIREMENT: 1) A document that identified the options available, and a few pro's and cons of each. EG. 1) Storing all files in the database with a BINARY/IMAGE data type. VS FILESTREAM VS Leaving the files outside of the database entirely. VS Other solutions 2) File server solution. EG: Extending the virtual drive to use multiple files to get past the current limits. VS A dedicated file server/SAN. VS Other solutions?