12 Nov 2018 by OriginalGriff
Don't store them in SQL server - store them as files (I'd use a GUID as the file name) and store the location plus the original filename in SQL. That way, you aren't clogging SQL with unnecessary data, using up huge amounts of SQL server bandwidth, and you make it easier to back up the whole...