>>We have an existing application that currently stores documents and other files as BLOBs directly in the SQL Server 2008 R2 database. It turns out the users are storing many more, and larger, documents than initially anticipated. To take the load off the database itself the plan is to store documents in a FileStream instead.
>>
>>Not having used FileStream before I thought I'd ask if anyone has any recommendations, any gotchas to look out for etc.
>>
>
>One thing to realize is that these files are NOT sent over the same port as SQL Server is. This is done over port 139/445 (the standard file sharing ports). This may or may not be an issue for you.
Hmm, that's interesting and definitely something to watch out for - thanks!
It looks like, when setting up a FileStream it's possible to allow or deny Win32(API?) access to the NTFS file store. I wonder if that setting has any effect on the port clients will use to pull files?
UPDATE: looks like it's required:
https://msdn.microsoft.com/en-us/library/dd283098.aspx
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
