What is Shredded Storage?
It’s a new Feature Introduced in SharePoint 2013 where Documents and Changes to the Documents are stored as “Shredded BLOBS”. Unlike SharePoint 2010, it helps to lower down the amount of storage required for saving files by saving only the Changes and not the entire Versions of the Files in database.
Some new additions that were made to support Shredded Storage in SharePoint 2013.
1. DocStreams Data Table - DocStreams is a new data table that gets created with each new Content database. This table contains File Blobs also known as “Shredded BLOBS” in individual rows.
2. BLOB Cache - As in SharePoint 2010 BLOB Cache enables a farm administrator to control the size of incremental reads when a client requests a file.
3. BLOB Index - Blob Index keeps track of various shreds and it’s his duty to make sure that a file can be reassembled when it is requested. It combines the entries of unchanged shreds of the previous versions of a file, with the new entries that point to the newly added changed shreds. This in whole creates a file to be served.
How it Works -
Every Document in SharePoint 2013 is now stored as multiple “shredded BLOBS” in the new “DocStreams” data table. Whenever a new Version of a document is created, a new Record is written in this data table that contains only the “Shred BLOB” of the original document that corresponds to the Change, merged with the new Changes. In other words a new Blob with Changes is added as a new row in the table. Each BLOB that gets added contains a numerical Id that represents the source BLOB. At the end it is the job of BLOB Index to keep the track of Blobs and to create a full file with the Combination of entries that point to the unchanged shreds of the previous version(s) and the entries that point to the newly added Changed shreds.
Benefits of Shredded Storage -
1. Shredded Storage Improves the I/O performance - In SharePoint 2010 in order to save the changes to a document or let’s say add a new version of a document, the original file is first read from the database server by the Web Server (WFE) and then it merges the document with Changes. The file is then sent back to the database server for storage. In this process results in a large amount of network traffic between the WFE and the database server.
In SharePoint 2013 however, when a Client updates a file, only the shredded BLOB that corresponds to the change is updated. This update occurs on the database server as opposed to the Web server(WFE) thus reducing huge network traffic and Improving File IO Operations.
2. Reduce Storage with Document Versioning - With Changes only being saved as “Changed Blobs” and not the entire document with the Changes as new Version, Shredded Storage helps Save a lot of Storage space and lowers the amount of storage required for storing files that are available in SharePoint.
It’s a new Feature Introduced in SharePoint 2013 where Documents and Changes to the Documents are stored as “Shredded BLOBS”. Unlike SharePoint 2010, it helps to lower down the amount of storage required for saving files by saving only the Changes and not the entire Versions of the Files in database.
Some new additions that were made to support Shredded Storage in SharePoint 2013.
1. DocStreams Data Table - DocStreams is a new data table that gets created with each new Content database. This table contains File Blobs also known as “Shredded BLOBS” in individual rows.
2. BLOB Cache - As in SharePoint 2010 BLOB Cache enables a farm administrator to control the size of incremental reads when a client requests a file.
3. BLOB Index - Blob Index keeps track of various shreds and it’s his duty to make sure that a file can be reassembled when it is requested. It combines the entries of unchanged shreds of the previous versions of a file, with the new entries that point to the newly added changed shreds. This in whole creates a file to be served.
How it Works -
Every Document in SharePoint 2013 is now stored as multiple “shredded BLOBS” in the new “DocStreams” data table. Whenever a new Version of a document is created, a new Record is written in this data table that contains only the “Shred BLOB” of the original document that corresponds to the Change, merged with the new Changes. In other words a new Blob with Changes is added as a new row in the table. Each BLOB that gets added contains a numerical Id that represents the source BLOB. At the end it is the job of BLOB Index to keep the track of Blobs and to create a full file with the Combination of entries that point to the unchanged shreds of the previous version(s) and the entries that point to the newly added Changed shreds.
Benefits of Shredded Storage -
1. Shredded Storage Improves the I/O performance - In SharePoint 2010 in order to save the changes to a document or let’s say add a new version of a document, the original file is first read from the database server by the Web Server (WFE) and then it merges the document with Changes. The file is then sent back to the database server for storage. In this process results in a large amount of network traffic between the WFE and the database server.
In SharePoint 2013 however, when a Client updates a file, only the shredded BLOB that corresponds to the change is updated. This update occurs on the database server as opposed to the Web server(WFE) thus reducing huge network traffic and Improving File IO Operations.
2. Reduce Storage with Document Versioning - With Changes only being saved as “Changed Blobs” and not the entire document with the Changes as new Version, Shredded Storage helps Save a lot of Storage space and lowers the amount of storage required for storing files that are available in SharePoint.
No comments:
Post a Comment