I upgraded SharePoint 2010 Farm using database attach method to SharePoint 2013. I have many site collections with their own databases. Overnight randomly one site collection database becomes huge from few MB to 70 GB or more on the sql Server. It is giving warning disk space is too low. I see one of the database and its log file have swelled very big more than 70 GB. If I go to the site collection corresponding to that database I don't see any content there all list and document libraries have same content. I don't know where to look for. I am not very good in sql Server. Any help will be appreciated. Thanks.

  • 1
    Do you use the Content Type Hub in your farm? If so, do you have a significant number of Content Types?
    – user6024
    Commented Apr 9, 2019 at 14:33
  • Do you have audit enabled on that site collection, it may be the case that night search crawl is causing massive swell on the audit data (if the view events are audited) Best way to see what is happening is to review the ULS logs for process is accessing that site. This way you will know where to look for culprit. Commented Apr 9, 2019 at 14:40
  • Thank You for your response. We don't use Content Type Hub. Also I checked on CA and Audit reports are not enabled. This thing happens randomly. One site collection swells overnight, next day I compress it through SSMS. Next day some other site collection swells. Sometime the swelled site collection have taken big space but it is empty. I can compress it. Sometime a table named DocStream is very big and I can not compress it through SSMS. Commented Apr 9, 2019 at 15:24

1 Answer 1


When we installed SharePoint 2013, we confused with Minimum Software requirements. For maximum we put the latest and greatest Software. In Minimum Requirements (Minimum Requirements ) there is Sql Server 2012. We used Sql Server 2017. This one caused the problem. Please read the software Requirements carefully. There is no Maximum Requirements. Only Minimum Requirements are tested and work. We changed Sql Server 2017 back to Sql Server 2012 and now everything is working fine. Thanks.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.