SQL Server 2005 database servicing an ASP.NET application (on a separate web servers).
DB has about 5GB of "normal" data in it, and about 15GB of "files" (e.g.: a 200k PDF stored as an image (BLOB), that sort of thing). More files are being uploaded by users, and are rapidly consuming more disk space (DB could grow to 50GB in the next few months, mostly files).
Storing so many files in the DB is already causing problems (e.g.: The large total size of the database makes occasional whole-DB backups and deployments difficult.).
And we are worried there will be more problems. (e.g.: performance issues - maybe caused by not being able to keep the whole DB in RAM, perhaps?)
What technical solution would you suggest to this problem? Store the files in the file system? Split the database in two and have a bigger, slower one for files?
Further Details if Needed:
These files are not super-important, and don't need very fast access times - a couple of seconds would be fine, and there are maybe a dozen selects per hour at most, currently. The other "normal" data in the DB includes info needed many times per second.