Ginneblog

Captain Kirk - a cloud pioneer

By default, when you upload a document or any other large file to SharePoint, it gets stored as a Binary Large OBject (BLOB) in the content database in SQL Server.  As revisions are made, each version of that file also gets stored (not just the differences).  The amount of BLOB data grows significantly faster than associated metadata, causing SharePoint to consume large amounts of expensive SQL Storage space.  Burzin talked about externalizing BLOB storage, as well as options for storing infrequently used BLOBs in the Cloud. These approaches can help ease the backup and storage cost problems content-heavy SharePoint sites encounter.

Burzin’s SharePoint Storage Best Practices talk also covered Configuration, Maintenance, and Performance Tuning.  He explained some of the unusual stresses SharePoint puts on SQL Server, and offered suggestions on how to avoid degraded performance.  If you’re planning a significant SharePoint implementation, you’ll want to take a close look at his specific recommendations regarding recommended I/O Capacities, Database configuration and sizing, processors and memory.

Given the headaches SharePoint BLOBs cause in many organizations, it makes sense that StorSimple has a complete solution to externalize them. Their storage-on-demand appliance provides tiered storage for SharePoint with the option to secure and store infrequently updated BLOBs to the cloud to achieve substantial cost savings.  According to Ursheet Parikh, StorSimple’s Founder and CEO, Burzin’s extensive SQL Server and SharePoint experience make him a key member of the StorSimple team.

I’ll write about StorSimple’s product in an upcoming post, and will follow that with a case study once DesignMind has had a chance to implement StoreSimple’s Cloud Storage Solution for one of our clients.  For data storage, Space is the Final Frontier.

Popularity: unranked [?]

 Send to Twitter