Reputation:
I have SQL Server 2012 and started looking into Filestream as a way to link "attachments" (> 1 GB) such as Excel documents and PDF files to database table records. While I have been successful in finding the "hello world" T-SQL examples that allow me to do some rudimentary tasks (enable Filestream, create table with Filestream column, insert row, etc.) I also encounter "beware" statements.
Is Filestream really as temperamental and full of "gotchas" as I the variously placed forum writings suggest, or is it straight forward and with a least predictable quriks?
Thank you for any insight
Upvotes: 2
Views: 1189
Reputation: 997
I would recommend using filetable which is implemented using filestream and its really neat enhancement, it preserves functionality of filestream but in contrast to filestream it can be configured to also allow accessing files outside db engine. For example, you can allow IIS to use those files directly. In production in big telecom company from 2013, flawless!
P.S. this is maybe more suitable for comment but I don't have reputation to write it :)
Upvotes: 2