Shredded storage in SharePoint 2013 in details

what is Shredded storage in SharePoint 2013, How Shredded Storage work in SharePoint 2013

Shredded means prepared by cutting or slice

Shredded storage is a new data storage platform improvement in SharePoint 2013 related to the management of large binary objects (I.e. BLOBS such as Microsoft PowerPoint Presentations, Microsoft Word Documents, etc.)

In this concept any contents we shave in list and document library stores separately than it is modified version, I mean for example if we have a word file shave in document library it will save in DocStream table in Content database, when we modify anything in this file and create a new version the modified what we add new things in existing file will save separate, earlier version sharePoint 2010 all files along with new changes used to save, it reduces the 70% storage space of your back end. Great features sir Ji.

A new data table created in SharePoint 2013 site collection database within each content database a new data table DocStreams exists where each shredded BLOB is stored in an individual row.

As we all know, documents stored in a library or as attachments are stored asbinary large objects (BLOBs) in the content database, by default. Remote BLOB Storage (RBS) is a set of APIs that let us to move BLOBs out of the SQL Server content database to another storage mechanism.

In SharePoint 2010, if version history is enabled on a document library, each new version results in a new BLOB for that document. Conceptually, a 1MB file with 10 versions is consuming 10MB of storage.

What a lot of people don’t consider is that a “new version” doesn’t mean just a change to the document– it can mean a change to metadata. So if a user changes a metadata field, that is a new version, and a copy of the BLOB is created, even if no change was made to the document itself!

At the highest level, what SharePoint 2013 shredded storage does is “chunk” or “page” the BLOB into numerous smaller shreds. So a single BLOB is now a construct made up of numerous shreds.

One result of this architecture is an effect similar to deduplication or single instancing: only differences are saved, not entire BLOBs. So, for example, if you have versioning enabled and a user makes a change to a document, only changed shreds are added to the storage footprint of that document. Shreds that have not changed from the previous version are simply “associated” with both versions.

We can see significant improvements in storage utilization. That same 1MB file with 10 versions may be consuming 2.2MB of storage, for example.

SharePoint 2013 allows content to be stored  as a collection of independent BLOBs (Shredded Storage). When shredded the data associated with a file such as Document.docx is distributed across a set of BLOBs associated with the file. The independent BLOBS are each assigned a unique ID (offset) to enable reconstruction in the correct order when requested by a user.

Shredded Storage is both improves I/O and reduces compute utilization when making incremental changes to document or storing documents in SharePoint 2013. Shredded Storage builds upon the Cobalt (I.e. File Synchronization via SOAP of HTTP) protocol introduced in SharePoint 2010.

it doesn’t do a merge and create a new whole BLOB binary of the new version of the document, it only stores the shreds or “deltas” as discussed in the SharePoint Conference 2012 keynote. When you open the latest version of the document, it combines the shreds and returns it to the WFE which in turn sends it to the client. The shreds are stored in a new table called DocStreams in the SQL Content Database allocated for the site collection, and a separate table keeps a list of all the pointers that make the overall BLOB up for that version.

Shredded Storage is enabled by default and cannot be disabled with any way, I mean uing UI, API or PowerShell Scripts

  1. DocStreams table stores any items modified version’s details.
  2. If content databases upgraded from SP2010 will have shredded storage applied so that existing version
  3. Shredded Storage also applies to historical versions – each version is not stored as a separate single blob.
  4. Microsoft Office 2013 is not required for Shredded Storage to work – any version of Office which accesses files via the DAV or the FSSHTTP protocol will benefit from this.
  5. Shredded Storage’s benefits don’t apply only to Microsoft Office file formats – any file format stored on SharePoint 2013 servers which is edited/updated by end users will benefit from Shredded Storage (keeping the cost of writing the update proportional to the change made to the file and lowering the footprint for historical versions).
  6. Shredded Storage is implemented by SharePoint 2013 and is supported by both SQL Server 2008 R2 Service Pack 1 and SQL Server 2012.
  7. A specific Office client is not required.

Turning Off Shredded Storage

Shredded Storage can be turned off for a web application, site collection, and site (web) level – the default setting is AlwaysDirectToShredded. If you turn off Shredded Storage, SharePoint goes back to acting like it did in SharePoint 2010…Cobalt v1 style. This means that you have potentially higher file i/o on between the WFE and no storage savings on deltas of versioned files.

About Krishana Kumar

Krishana Kumar is SharePoint Architect/Trainer having Architecture experience with high volumes at Enterprise level and global scale - creation of highly scalable solutions with global user base and geographically distributed architectural components. Good knowledge of SharePoint best practices and governance models. I hold Two Master degree in Computer Science with over 11 years of experience working on Microsoft Technologies specially SharePoint, Project, .NET and other Information Worker Technologies. Having good exposer in Client side scripting Angular.js, backbone and Node. I am currently responsible for SharePoint Infrastructure set up and leading teams in various medium and large scale projects, architecting, designing & installing SharePoint farms, developing custom components,, and providing advanced SharePoint administration and development training to teams and customers. I regularly speaks in various SharePoint User Groups and other Events. I have MCSA Windows Azure, MCSA Office 365, MCSE & MCSD SharePoint 2013, Microsoft Certified Developer (MCD) and holds MCPD, MCTIP and MCTS for SharePoint 2010, MCTS MOSS 2007 & WSS 3.0, MCPD, MCITP (EPM 2010 & 2007) and MCSD .NET.
This entry was posted in General Interest. Bookmark the permalink.