Developing the site hierarchy is only one aspect of a successful implementation. Understanding the boundaries and limits of SharePoint 2010 is critical to ensuring scalability, performance, and manageability. This is especially important in the planning of Content Databases as they naturally align to the site hierarchy and impact performance and usability. A site hierarchy with poorly planned Content Databases creates a situation where costly remediation is necessary in order to scale the platform properly. The following charts and guidance are offered to assist in capacity planning. Source: TechNet

Index

This section provides limits sorted by the logical hierarchy of a SharePoint Server 2010 farm and features.

Recommendations

Capacity Planning has implications across multiple areas of the SharePoint Architecture. While there are many facets to Capacity Planning, the following offers insights into Content Database creation and maintenance within SharePoint 2010:

1. Follow Microsoft’s Recommendation for Content Databases

   Limit the size of content databases to 200 GB to help ensure system performance. Content database sizes up to 1 terabyte are supported only for large, single-site repositories and archives with non-collaborative I/O and usage patterns, such as Records Centers. Larger database sizes are supported for these scenarios because their I/O patterns and typical data structure formats have been designed for, and tested at, larger scales. A site collection should not exceed 100 GB unless it is the only site collection in the database.

2. Use Quota Templates to Provide Alerts and Enforce Size Limits

   The use of Quota Templates will allow for alerts and enforcement of maximum size limits. This is especially critical for project sites in which projects are continually added and additional Content Databases may need to be created to accommodate for new projects. By configuring an alert to trigger at 80% capacity, you will be able to create a new Content Database and place new project sites within the new database. This will still leave 20% capacity for existing project sites, and a scalable/manageable methodology for bringing new project sites and Content Databases online.

Print PDF

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23