Our team recently watched FILESTREAM to expand the capabilities of our proprietary application. The main goal of this application is to manage various PDFS, images and documents for all parts that we produce. Our ASP application uses several third-party tools to view these files. Currently, we have 980 GB of data on the File Server. We have about 200 GB of binary data on SQL Server that we would like to extract, since it does not work well, so FILESTREAM seems to be a good compromise for the two main data storage / access issues.
Several things are not entirely clear to us:
FILESTREAM May or may not store its data on a disk that is not connected locally. We already have a file server with RAID 10 disks (1.5 TB). All documents are stored on this server right now, do I need to move these disks to SQL Server for FILESTREAM? It will be a tough bullet to bite, as the server also doubles as an application server (two virtual machines on the same physical server).
FILETABLE stores general metadata about files, but where is the full text part stored to allow searching for files such as doc / docx? Is it separate? Can you freely add criteria to this for your search? If so, any links for clarification will be clarified.
Is it possible to reference FILETABLE in another table with a foreign key?
Thank you in advance
EDIT: , -, FILESTREAM 2008 2012 cavets ( , ): http://channel9.msdn.com/Events/TechDays/Techdays-2012-the-Netherlands/2270
FILESTREAM, .
2:
# 1 - FileTable FILESTREAM . ( , ). , , SQL .
# 2 - , -, : http://channel9.msdn.com/Events/TechEd/Europe/2012/DBI411
# 3 - TFT, Docs, ( ), . .