To configure SharePoint Remote BLOB Storage (RBS) with Microsoft’s FILESTREAM provider, enable FILESTREAM on the SQL Server hosting the content databases, provision a FILESTREAM store for each database, install the RBS client on the SQL and relevant SharePoint servers, and activate RBS separately for each content database. Finish by testing an upload and confirming that your backup, restore, and storage operations account for externalized files. Follow Microsoft’s FILESTREAM installation procedure and RBS overview.
What RBS changes—and what it does not
RBS moves BLOB data, such as document contents, out of a SharePoint content database into a separate store. SharePoint continues to manage access to that content. Microsoft states that “All access must occur by using SharePoint Server only”; do not edit, move, or delete externalized BLOBs directly with file-management tools or other applications. See Microsoft’s RBS overview.
The configuration has two scopes: prepare the SQL Server and install the client components for the farm, then provision and enable RBS for each target content database. The FILESTREAM settings are configured on each relevant database server; the BLOB store and SharePoint activation are per content database.
Check prerequisites and permissions
First confirm that your SharePoint release, SQL Server version and edition, provider package, and topology are compatible. Microsoft’s installation procedure maps SharePoint releases to RBS client packages included in supported SQL Server Feature Packs. Use the package specified for your combination rather than assuming one installer applies to every farm.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
Make sure the accounts used for each operation have the required rights:
- Provision a store:
db_owneron each target content database. - Install the RBS client: local Administrators membership on every server where the client library is installed.
- Enable RBS from SharePoint Management Shell: SharePoint PowerShell access,
securityadminon the SQL instance,db_owneron the databases being updated, and Administrators membership on the SharePoint server used for activation.
These prerequisites are listed in Microsoft’s installation procedure.
Configure the FILESTREAM provider
1. Enable FILESTREAM on each relevant SQL Server
On each SQL Server hosting a content database you plan to use with RBS, enable FILESTREAM for Transact-SQL access and file I/O streaming access. Enable remote client streaming access only if your topology requires it. Restart the SQL Server service after changing the configuration. Follow Microsoft’s FILESTREAM configuration guidance.
2. Create a FILESTREAM store for each content database
In SQL Server Management Studio, connect to the SQL instance that contains the target content database and run Microsoft’s statements in order. Replace WSS_Content and the example path with your database name and planned storage directory. The password shown is illustrative; use an appropriate secret for the database master key.
Free tools Windows power users keep installed
One-click scans. No signup required.
USE [WSS_Content];
IF NOT EXISTS (
SELECT * FROM sys.symmetric_keys
WHERE name = N'##MS_DatabaseMasterKey##'
)
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'Admin Key Password !2#4';
USE [WSS_Content];
IF NOT EXISTS (
SELECT groupname FROM sysfilegroups
WHERE groupname = N'RBSFilestreamProvider'
)
ALTER DATABASE [WSS_Content]
ADD FILEGROUP RBSFilestreamProvider CONTAINS FILESTREAM;
USE [WSS_Content];
ALTER DATABASE [WSS_Content]
ADD FILE (NAME = RBSFilestreamFile, FILENAME = 'c:Blobstore')
TO FILEGROUP RBSFilestreamProvider;Provision the store once for each content database you intend to use with RBS. Microsoft recommends placing it on a volume separate from the operating system, paging files, database data and log files, and tempdb. See the documented provisioning procedure.
3. Install the RBS client components
Install the compatible RBS client on the SQL Server and on each relevant SharePoint front-end and application server. Microsoft specifically cautions against launching the MSI wizard for this SharePoint configuration because its defaults are not recommended; use the documented command-line procedures instead. Installation parameters vary by server role, database, SQL instance, and package, so use the values and commands in the current Microsoft installation instructions rather than copying a command with unmodified example values.
Check the installation log for the confirmation Product: SQL Remote Blob Storage - Installation completed successfully.
4. Enable RBS for each content database
On a farm server where the RBS client is installed, open SharePoint Management Shell and run the activation for one target database. Replace the placeholder with its actual content database name:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
$cdb = Get-SPContentDatabase <ContentDatabaseName>
$rbss = $cdb.RemoteBlobStorageSettings
$rbss.Installed()
$rbss.Enable()
$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])Repeat the operation for every content database that will use RBS. If more than one provider is installed, verify the provider names and select the intended one; do not assume the first name returned is correct. Microsoft documents this activation sequence in its RBS installation procedure.
Rank #4
5. Test the store with a SharePoint upload
Start with an empty RBS store, then upload a file through a SharePoint document library. Check that the file is written to the store, as described in Microsoft’s installation test. In your own farm, also validate application behavior, monitoring, backup and restore, and recovery from a store or connectivity failure before relying on the configuration in production.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check version and topology requirements before choosing a provider
FILESTREAM is Microsoft’s documented built-in provider route. For remote RBS, Microsoft’s overview lists these SQL Server requirements for the server holding the RBS metadata:
| SharePoint release | SQL Server requirement for remote RBS metadata |
|---|---|
| Subscription Edition | SQL Server 2019 or later, Enterprise edition |
| SharePoint Server 2019 | SQL Server 2016 or 2017, Enterprise edition |
| SharePoint Server 2016 | SQL Server 2014 SP1, Enterprise edition |
| SharePoint 2013 | SQL Server 2008 R2, 2012, or 2014, Enterprise edition |
These are release-specific statements in Microsoft’s RBS overview for the SQL Server storing RBS metadata; they are not a complete compatibility matrix for every remote BLOB-store topology. Check the current SharePoint and SQL Server support lifecycle, patch level, topology-specific requirements, and provider documentation before implementation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsMicrosoft also documents a Remote Share Provider for offloading BLOB storage to SMB storage. Its availability does not establish that it suits every farm. Evaluate the provider’s version and topology requirements, installation and maintenance process, storage ownership, and recovery plan against your needs.
If you use a third-party provider
Installation steps differ by provider. Follow the manufacturer’s instructions for its components, then complete the SharePoint-side setup, activate the provider for each applicable content database, and test a file upload. Microsoft’s third-party provider procedure describes this general approach; it does not replace the provider’s own requirements.
Plan backup, restore, and storage operations
Provider choice affects farm database protection. Microsoft says FILESTREAM is the only provider currently supported for SharePoint Server farm database backup and restore operations. Site collection backup and restore, and site import and export, use deep copy: file contents pass through SharePoint regardless of provider. Account for those different paths when planning backup windows, capacity, and recovery procedures. See Microsoft’s RBS backup and restore guidance.
Quick Recap
- Keep externalized BLOB access and maintenance within SharePoint’s supported access path; do not manipulate BLOB files directly.
- Confirm that your backup and restore procedure covers the content database and the externalized BLOB data it references.
- Test recovery and application behavior in the actual farm before treating a successful upload as sufficient validation.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
