Access your Pro+ Content below.
SharePoint 2010 remote BLOB storage: A ‘large’ step up on storing data
This article is part of the December 2011 issue of SharePoint Insider
Since SharePoint was first released, Microsoft has used SQL Server as the underlying data management and storage mechanism. Although SQL Server is adequate for storing SharePoint data, it isn’t always ideal. The reason for this is that like most relational databases, SQL Server is optimized for storing structured data, such as configuration, table and list data. However, the files that are typically stored in SharePoint document libraries are not structured. When a user saves a file to a SharePoint document library, that file is saved to the SQL Server database as blob, or binary large object, data. There is no rule that says blob data can’t be kept in SQL Server, but SharePoint Server 2010 provides the option of moving it out of content databases and into less costly storage resources through Microsoft’s Remote BLOB Store add-on software. Architecturally, SharePoint 2010 remote blob storage is somewhat similar to SQL Server storage. The blob data isn’t merely offloaded onto a file share. Instead, an external storage medium (...
Access this Pro+ Content for Free!
Features in this issue
Creating an effective governance plan before a SharePoint 2010 implementation project begins, and managing it properly, can help assure smooth deployment, enterprise-wide adoption and success.
Organizations should plan implementation of SharePoint 2010 deployments early and carefully so adoption grows according to policies and the enterprise reaps the best return on investment.
SharePoint Server 2010 uses SQL Server for storage and while optimized for structured data, most files in SharePoint libraries are unstructured and copies might be better saved as remote BLOB storage.