Site Collection size cause

Question

We have a site collection that has couple of document libraries each having 10K documents. And the content DB assigned to that site collection is showing 280 GB used. But when we check the library size using the following powershell -

    $total = $null; 
 ((get-spweb http://sitename/).lists | Where-Object {$_.title -eq "List   name"}).items | foreach {$total+= $_.file.length}; $total /1MB  

we get 40 GB as total size for both libraries. Are we missing anything, what would be the cause of the remaining size that is being used up in content Db.

Please find snapshot of content DB Usage by table report

Answer 1

In SharePoint 2010, versioning stores complete copies of previous versions. The size you are seeing is all the previous versions.

Some things to combat this, in your versioning settings in the libraries, set maximum number of major and minor versions. After setting that, you'll need to perform some scripted maintenance to purge the versions.

You would want to check out each file, check it in, and publish it as a major version. You will then see file size decrease. You won't see the database size decrease though unless you shrink the database, but that is not generally a recommended practice.

Answer 2

AllDocStreams stores the actual binary content of a document. In 2010, this would store the binary content of each file, while in 2013/2016 it would only store the difference from the previous version.