June 28, 2012 at 8:55 am
I have a developer working on a new business requirement that must allow our users to upload files to the database. We normally stored the files on the web server and have pointers in our database to reference them. However, the new requirement says users must be able to quickly search names as well as content of these uploads.
Our file system on the web server does not employ indexing currently, but we could turn on file level indexing on the disk and upload files there and make remote calls to search the web disk files for content, but I fear that will be super-slow. The other option we thought of is enabling Full Text search and storing the files in the database. However I fear that could create file size growth issues and increase backup and maintenance windows having those BLOBs in the database?
Any experts in the area have any input on what a realist and scalable solution would be?
June 28, 2012 at 9:04 am
if it's a new development have you considered moving to SQL 2008/2012 and using filestream ?
i've used the file full text search before and it leaves you at the mercy of the indexing.. the number of times it went wrong or stopped working was higher than when it actually did work
MVDBA
June 28, 2012 at 9:11 am
We have, but 2012 is still at least one year or more out for us. Thanks!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply