FILESTREAM with SharePoint 2010

while roaming around over the net found a very nice article on File Stream and SharePoint 2010. I’m sharing the same article with you all.
FILESTREAM Overview
FILESTREAM is implemented on the varbinary(max) datatype instructing the database engine to store unstructured data on the file system through a FILESTREAM filegroup that contains file system directories instead of the files themselves also known as data containers. Data containers are the interface between database engine storage and file system storage. varbinary is the binary data type designation for binary large objects stored in SharePoint 2010 content databases and refers to variable-length binary data. (MAX) refers to a value that max indicates that the maximum storage size is 2^31-1 bytes or otherwise 2GB. Remote BLOB Storage does not provide a mechanism to exceed to the 2GB file size limit imposed by SharePoint.
In SharePoint 2010 remote BLOB data is referenced by a unique identifier in content databases configured for RBS (see illustration).

FILESTREAM offers several benefits as related to performance 1) FILESTREAM uses the NT system cache for caching file data reducing the effect that FILESTREAM data has on Database Engine performance and 2) the SQL Server buffer pool is not used; therefore, memory is available for query processing.
FILESTREAM provides optimum value in scenarios where SharePoint is used to storage large BLOB data such as video files that will benefit from FILESTREAM or BLOB data that exceeds 1MB.
Special Considerations
FILESTREAM and Business Continuity Management
Database mirroring does not support FILESTREAM since a FILESTREAM filegroup cannot be created on the principal server and database mirroring cannot be configured for a database that contains FILESTREAM filegroups. If the FILESTREAM provider is used to store BLOB data locally (within the same content database) the database cannot be configured for database mirroring.
If the FILESTREAM provider is configured to store the BLOB data within a separate SQL database or when using a 3rd party BLOB store, the content database can be mirrored; however, database mirroring will apply only to the content database and not the BLOB data. The BLOB data needs to be handled separately and kept in sync with the associated metadata (content database). For FILESTREAM BLOB databases, this can be done through log shipping.
To learn about the differences between FILESTREAM and SQL Server Remote BLOB Store see also http://blogs.msdn.com/b/sqlrbs/archive/2009/11/18/sql-server-remote-blob-store-and-filestream-feature-comparison.aspx.
FILESTREAM and the Office Web Applications Cache
The Office Web Applications cache is used by Word and PowerPoint Web Applications to create a version of a document requested for viewing through the browser improving performance and reducing resource consumption on server machines by making cached versions of a document or presentation available in cases where there are multiple requests for the same document. 
The Office Web Applications cache occurs in two (2) distinct tiers, on the server file system and within a “specialized” site collection hosted on a per Web application basis. Document or presentation requests made through the Office Web Applications are served through both caches as the images are rendered for client consumption. Both cache locations are used by all site collections within a Web application where the Office Web Applications features activated.
Content databases where FILESTREAM is configured will store the cached versions of the document or presentation in the configured provider location.  It is recommended to configure the Office Web Applications cache on a database that is not configured for FILESTREAM.
Configuring FILESTREAM with SharePoint 2010
The instructions that follow are designed to be used on a single-server deployment for demonstration purposes and implements the local FILESTREAM Provider.
Enable FILESTREAM on the target SQL Server Instance
1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2008 (R2), point to Configuration Tools, and then click SQL Server Configuration Manager.
2. In the list of services, right-click SQL Server Services, and then click Open.
3. In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
4. Right-click the instance and then click Properties.
5. In the SQL Server Properties dialog box, click the FILESTREAM tab.
6. Select the Enable FILESTREAM for Transact-SQL access check box.
7. If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
8. If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
9. Click Apply.
10. Click Start, click All Programs, click Microsoft SQL Server 2008 (R2), and then click SQL Server Management Studio.
11. In SQL Server Management Studio, click New Query to display the Query Editor.
12. In Query Editor, enter the following Transact-SQL code:
EXEC sp_configure filestream_access_level, 2
In Query Editor, enter the following Transact-SQL code:
RECONFIGURE
Provision the RBS Data Store
1. Click Start, click All Programs, click Microsoft SQL Server 2008 (R2), and then click SQL Server Management Studio.
2. Expand Databases.
3. Select the content database for which you want to create a BLOB store, and then click New Query.
4. In SQL Server Management Studio, click New Query to display the Query Editor.
5. In Query Editor, enter the following Transact-SQL code:
use [Database Name]
if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Admin Key Password !2#4'
In Query Editor, enter the following Transact-SQL code:
use [Database Name]
if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider')alter database [Database Name] add filegroup RBSFilestreamProvider contains filestream
In Query Editor, enter the following Transact-SQL code:
use [Database Name]
alter database [Database Name] add file (name = RBSFilestreamFile, filename = 'c:\BlobStore') to filegroup RBSFilestreamProvider
Install the Microsoft SQL Server 2008 R2 Remote Blob Store
Download the x64 package for the Microsoft SQL Server 2008 R2 Remote Blob Store from the Microsoft SQL Server 2008 R2 Feature Pack at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52&displaylang=en.
Open a Command Prompt with Administrator permissions and execute the following command to install RBS.MSI downloaded in the previous step:
msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="<Database Name>" DBINSTANCE="<Instance Name>" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
NOTE
Specify the full path to RBS.MSI in the above state, i.e. C:\Users\Administrator\Desktop\RBS.MSI. Replace the values for DBNAME and DBINSTANCE to match your environment.
Enable Remote BLOB Storage
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to set the content database to be configured:
$database=Get-SPContentDatabase –Identity “Database Name”
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to gets the object that holds settings that determine how the content database uses Microsoft SQL Server Remote Blob Storage:
$rbs=$database.RemoteBlobStorageSettings
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to determine if RBS has been installed for the selected content database:
$rbs.Installed()
NOTE
The result of $rbs.Installed() should be True, if the result is False, verify RBS.MSI has been installed successfully by reviewing rbs_install_log.txt. Ensure the install statement was running In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to enable RBS for the selected content database:
$rbs.Enable()
In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to set the RBSprovider for the selected content database:
$rbs.SetActiveProviderName($rbs.GetProviderNames()[0])
$rbs
NOTE
The result of $rbs should be:

Table 1
Appendix for Table 1
Enabled specifies whether or not RBS has been enabled for the selected content database.
ActiveProviderName is name of the SQL Remote Blob Storage provider new files will be stored in. This will be null if new files will not be stored using SQL Remote Blob storage.
MinimumBlobStorageSize refers to the minimum size a BLOB may be to be considered RBS storage worthy, BLOB data exceeding the specified MinimumBlobStorageSize will be stored in the RBS data store.
FILESTREAM performance data shows BLOB data exceeding 1MB provides the most efficient streaming performance. See also http://msdn.microsoft.com/en-us/library/cc949109(SQL.100).aspx.

To configure the MinimumBlobStorageSize:
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statements to configure the MinimumBlobStorageSize at 1MB:
$database = Get-SPContentDatabase “Database Name”
$database.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576
$database.Update()
UpgradePersistedProperties specifies the collection of field names and values for fields that were deleted or changed.
Validate Installation
To validate the FILESTREAM configuration and RBS installation:
1. Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.
2. Expand Databases.
3. Select the content database for which you want to create a BLOB store, and then click New Query.
4. In SQL Server Management Studio, click New Query to display the Query Editor.
5. In Query Editor, enter the following Transact-SQL code:
USE [Database Name]
SELECT * FROM dbo.DatabaseInformation
Confirm that both the RBSCollectionId and RBSProvider rows are available.
Test the RBS Data Store
1. Select a desired Document Library on a site in the configured content database.
2. Upload a file that is greater than 1 MB.
3. On the computer that contains the RBS data store, click Start, and then click Computer.
4. Browse to the RBS data store directory.
5. Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly.
The data store directory structure will appear similar to that in the following diagram.