Content databases are growing too large in SharePoint 2013/2016
Check out Best Alternative to InfoPath -> Try Now
This SharePoint tutorial explains. the solution for content databases are growing too large in SharePoint 2013. The SharePoint 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.
Content databases are growing too large in SharePoint 2013
Edit the rule definition to prevent new sites from being added to these databases, and then move some site collections to other databases.
- Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
- On the Central Administration Home page, click Monitoring.
- On the Monitoring page, in the Health Analyzer section, click Review rule definitions.
- On the Health Analyzer Rule Definitions page, in the Availability category, click the name of the rule.
- In the Health Analyzer Rule Definitions dialog box, click Edit Item, and then select the Repair Automatically checkbox.
- Click Save. You can no longer add new sites to databases that exceed 100 GB. You can set more than 100GB for the site as a limit. It depends on your HDD capacity.
You may like following SharePoint content database tutorials:
- Backup and Restore content database SharePoint 2013
- Get Content DataBase Size Using PowerShell in SharePoint 2013
- Prevent new sites to be added to content databases in SharePoint 2013
- Get content database sizes for all web applications in a SharePoint farm using PowerShell
- Move Site Collections to other content databases in SharePoint 2013
- Find content database name for site collection using PowerShell in SharePoint 2013/2016
This SharePoint learned how to solve Content databases are growing too large in SharePoint 2013 issue.
SharePoint Online FREE Training
JOIN a FREE SharePoint Video Course (3 Part Video Series)