In this post, we’ll compare SharePoint 2016 Content Database limits with content database limit SharePoint 2013.
We’ll also discuss the SharePoint 2016 Content Database Limits by exploring the following:
-
1
SharePoint 2016 Content Database Limits
- 1.1 How many content databases per farm in SharePoint 2016?
- 1.2 How many content databases per web application in SharePoint 2016?
- 1.3 What’s content database size in SharePoint 2016?
- 1.4 How many site collections per content database in SharePoint 2016?
- 1.5 How many content database items per content database in SharePoint 2016?
- 2 SharePoint Content Database Limits Summary
You might also like to read SharePoint 2019 Limitations.
In this section, we’ll explore the below SharePoint 2016 Content Database Limits:
- Content databases per farm.
- Content databases per web application.
- Content database size (General Usage).
- Content database Size (All Usage).
- Site collection per content database.
- Content database items.
You might also like to read Get All Content Databases Per Farm using PowerShell.
The number of content databases per farm in SharePoint 2016 is 500 content databases.
The number of content databases per web application in SharePoint 2016 is not specified. however, the web application can hold the max number of content databases per farm that is 500 content databases.
Note: the supported number of web applications per farm is 20 web applications, so if you are planning to create 20 web applications you can consider the supported content databases per web application is 25 content databases. (500 content database /20 web application) = 25.
- In general usage, the content database size in 200 GB up to 1 TB.
- In all usage, the content database size is 4 TB.
The number of site collections per content database in SharePoint 2016 is 10,000 site collections.
It’s strongly recommended limiting the number of site collections in a content database to 5,000. However, up to 10,000 site collections in a database are supported.
The number of content database items per content database in SharePoint 2016 is 60 million items including documents and list items.
You might also like to read SQL Server Best Practices for SharePoint 2019
The following table lists the recommended guidelines for SharePoint 2016 Content database limits compared to
- Content database limit SharePoint 2013,
- Content database limit SharePoint 2010,
- Content database limit SharePoint 2007.
You might also like to read PowerShell Script: SharePoint Farm Scan Report
Limits | SharePoint 2007 | SharePoint 2010 | SharePoint 2013 | SharePoint 2016 |
Content databases per farm |
x |
x | 500 per farm | 500 per farm |
Content databases per web application | 100 per web application | 300 per web application |
x |
x |
Content database Size (General Usage) | 100 GB | 200 GB | 200 GB | 200 GB up to 1 TB |
Content database Size (All Usage) | > 100 GB | 4 TB | 4 TB | 4 TB |
Site collection per content database | 50,000 per content database | 2,000 recommended 5,000 maximum | 10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone) | 5,000 recommended 10,000 maximum |
Content database items |
x | 60 million items including documents and list items | 60 million items including documents and list items | 60 million items including documents and list items |
Remote BLOB Storage | x | < 20 millisecond | Remain within 40 milliseconds 95% of the time. | Remain within 40 milliseconds 95% of the time. |
Conclusion
In conclusion, we have explored SharePoint 2016 Content Database limits compared to content database limit in SharePoint 2013, 2010.
Applies To
- SharePoint 2016.
- SharePoint 2013.
- SharePoint 2010.
- SharePoint 2007.
Download
Download PowerShell Script: SharePoint Farm Scan Report to get statistics and monitor the limits in your SharePoint farm.
You might also like to read
- SharePoint 2019 Limitations.
- Site Collection limits SharePoint 2016.
- SharePoint 2016 Web Application Limits.
- SharePoint 2016 Application Pool Limits.
- SharePoint 2016 List and Library Limits.
- SharePoint Boundaries Vs Thresholds Vs Limits.
References
Have a Question?
If you have any related questions, please don’t hesitate to Ask it at deBUG.to Community.
very valuable comparison
Glad to hear it helped you!
Extremely Helpful! Thank you for such a well-written article. I have bookmarked for future reference.
Great comparison, thanks for sharing!
Pingback: SharePoint 2019 Limitations | SPGeeks
Pingback: SharePoint 2010 Limitations | SPGeeks