How to install the RBS FILESTREAM Provider in a SharePoint 2010 system

These two days in the study of how to write a RBS Provider, unfortunately the document is very scarce, basically in addition to a spec, only the SQL product group wrote a sample. Then if the research has results, then put it into the article, now let's talk about how to install and use the RBS FILESTREAM Provider directly.

If you use SharePoint 2007 as your document management platform, it's a big criticism that SharePoint 2007 stores the file itself directly in the SQL Server database. Although Windows SharePoint Services 3.0 SP1 adds a external BLOB Storage (EBS) interface, Microsoft does not provide implementations, but rather requires developers to implement it themselves.

SharePoint 2010 still provides compatibility for EBS, but it is not recommended for EBS, but the recommended solution is to use SQL Server 2008 Remote BLOB Storage (RBS).

SQL RBS is a set of APIs that, through RBS, no longer requires a SQL Server 2008 database to store a sophomore data (BLOB) inside a database, but rather to be stored somewhere outside, where a reference to external BLOB data may be stored in the database. Both SQL Server 2008 and SQL Server 2008 R2 support RBS.

It sounds as if RBS is a really good thing. But (always), RBS is just a set of APIs, in other words, RBS allows developers to exploit this set of APIs to develop a RBS Provider that really enables access to BLOB data. Without the RBS provider,rbs itself, the blob will not be automatically stored in a specified place. Different RBS Provider allows us to store blobs in a variety of places, such as file systems, disk storage devices, file servers, and so on, anyway, without going on to the SQL Server database.

After you have an initial understanding of RBS, we go on to introduce another new feature in SQL Server 2008: FILESTREAM. The following sentence is excerpted from SQL Server 2008 Books Online: "by storing varbinary (max) binary large object (BLOB) data as a file on a file system, FILESTREAM makes the SQL Server database engine and the NTFS file system a A whole. "So, FileStream can have the administrator choose to store the varbinary (max) type BLOB data inside the SQL Server database on the local NTFS file system. The benefits of database transaction processing can also be enjoyed while accessing BLOB data through FileStream.

Sounds like FileStream and RBS are very similar, don't they? But in fact, RBS and FileStream are two different things, and they are not dependent on each other. RBS is a set of API interfaces through which the application can store BLOB data somewhere outside the database and implement the RBS provider created by the developer. FileStream is a built-in feature of SQL Server 2008 that stores the BLOB data that was originally stored in the database on the local NTFS file system on the server.

SharePoint 2010 Exploits the RBS API, not the FileStream feature. So without a RBS Provider, we can't immediately store files stored in SharePoint 2010 somewhere outside the database. However, since the FILESTREAM feature already has the ability to store BLOB data from a database on an NTFS file system, why not use FILESTREAM directly, and do a RBS FILESTREAM Provider, What about a RBS provider that is implemented using FileStream's functionality? So, is it possible to store the files in SharePoint 2010 on the NTFS file system?

Microsoft also thought of it, so Microsoft provided a RBS FILESTREAM Provider in the form of a Feature Pack (Feature pack). You can download the x64 version of the RBS FILESTREAM Provider from here. However, to install and use it on a SharePoint 2010 system, you also need to follow certain steps. Here is the specific procedure.

1. Determine that SQL Server 2008 has FileStream enabled

When you install SQL Server 2008, there is a step that prompts you to install FileStream. If you are unsure whether to install this feature, open SQL Server Configuration Manager from the SQL Server 2008 server, select SQL Server service from the left, and then right-click the running instance of SQL Server from the right pane and select the Properties menu item.

In the Open Properties window, select the FILESTREAM tab, and then select the Enable FILESTREAM selection box and click OK.

Open SQL Server Management Studio, select the instance of SQL Server on the left, click New Query in the toolbar area, open a query interface, and then enter the following SQL statement inside and execute.

EXEC sp_configure filestream_access_level, 2

Reconfigure