External Storing of Binary Large Objects (BLOBs) in Windows SharePoint Services
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The Help topics in this section describe how to use the special external binary large object (BLOB) store provider (EBS Provider) interface, ISPExternalBinaryProvider, to allow you to store BLOB data in a data store that is external to the SharePoint content database. Topics in this section discuss the rationale for storing BLOB data externally, the architecture of the EBS Provider, and implemention of the EBS Provider in front-end Web applications for Windows SharePoint Services.
Typically, as much as 80 percent of data for an enterprise-scale deployment of Windows SharePoint Server consists of file-based data streams that are stored as BLOB data. These BLOB objects comprise data associated with SharePoint files. However, maintaining large quantities of BLOB data in a Microsoft SQL Server database is a suboptimal use of SQL Server resources. You can achieve equal benefit at lower cost with equivalent efficiency by using an external data store to contain BLOB data.
Help topics in this section describe the programming interface and the implementation architecture that allows you to deploy a cost-effective external data store for BLOB data. Additionally, the discussion provides important technical information to support a trade-off analysis to determine the costs and benefits of accepting some degree of added complexity in exchange for lower operational costs.