I'm seeking some advice regarding the best option for setting up SQL Server 2012.
A project has started to replace our in-house document management system. The scenario is that users create a document wallet that they add various documents to. Certain documents could be worked on via the front end of the system, in doing so
a new version of the document is created.
Various meta data is stored regarding the documents and the wallet itself which is searchable. A wallet has an active lifespan of approx 5 years where documents could be added or worked on. During the 5 year process, wallets could be marked as
terminated or complete and become read only.
The current system has approx 1TB of documents stored within the mysql db. All documents are stored as single page Tiffs.
We are trying to evaluate the best option for using SQL Server the current thinking is to use a file table to store the documents however I'm leaning more towards RBS.
Can anyone offer me some real-life pro's and cons of the two that may sway our design?
Using the FileTable feature, organizations can now store files and documents within a special table in SQL Server and they will have the ability to access those files and documents from windows. When you use this feature it will appear to you as if the files
and documents are residing on a file system rather than in SQL Server. However, in order to use the FileTable feature you need to enable the FILESTREAM feature on the instance of SQL Server 2012. Follow the steps mentioned in this tip,
Different ways to enable FILESTREAM feature of SQL Server 2008
Here is a particular blog which describes how to use filetable feature: