Content databases are growing too large in SharePoint 2013

InfoPath alternatives for form designing SharePoint

In this post we will discuss about the solution for content databases are growing too large in SharePoint 2013.

Also you can check out my previous posts on:

– Difference between Sharepoint 2010 and Sharepoint 2013

– Enable Anonymous access to a SharePoint 2013 site

– Different authentication types supported in SharePoint 2013

The content databases have grown larger than 100 gigabytes (GB). Large content databases can be difficult to back up and restore. They are also more likely to cause the application to stop responding when you perform operations that affect entire databases.

Resolution:
Edit the rule definition to prevent new sites from being added to these databases, and then move some site collections to other databases.

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

2. On the Central Administration Home page, click Monitoring.

3. On the Monitoring page, in the Health Analyzer section, click Review rule definitions.

4. On the Health Analyzer Rule Definitions page, in the Availability category, click the name of the rule.

5. In the Health Analyzer Rule Definitions dialog box, click Edit Item, and then select the Repair Automatically check box.

6. Click Save. You can no longer add new sites to databases that exceed 100 GB.You can set more than 100GB for site as limit.it depends on your HDD capacity.

Similar SharePoint 2013 Tutorials


Leave a Reply