Longtime lurker here, and I finally have a question.
We have an existing product with a file archive as part of the feature set. Currently files are stored in MSSQL in the same database as the rest of the data. This isn't ideal, since it leads to long backup/restore cycles, not great performance, and expensive database SSD storage. The larger instances (single tenant) are ~2-3 TB of which 90% are files, but we predict file archive usage only going up.
Requirements: - On premise hosting - Search file contents (Word/Excel/PPT support) - Good backup support (differential backups would be great!)
I haven’t used it, but it seems designed for that use case (FTA: “If you do not want to back up FILESTREAM data with relational data, you can use a partial backup to exclude FILESTREAM filegroups.”)