Datasheet

38
|
CHAPTER 1 SharePoint Foundation 2010 under the hood
Table 1.3: Software limitations for SharePoint Foundation 2010
Object Maximum value Type of object limit Details
Content
Database
300 per web
application
Web application limit With 300 content databases per web
application, end users may not see a
change in performance, but admin-
istrative operations such as creating
a new site collection will experience
a decrease in performance. Using
PowerShell for administration
might help.
Managed
Paths
20 per web
application
Web application limit Managed paths are cached on the web
server, and beyond 20, there is a deg-
radation in performance.
Application
Pools
10 per web server Web server, application
server limit
It does depend on the server’s RAM
and the workload the farm is servic-
ing. However, this is a good rule of
thumb. If you need more, test thor-
oughly for performance issues.
Content
Database Size
200 GB per
database
Content database limit There is no hard limit, but it is
strongly suggested to limit individual
content databases to 200 GB apiece.
Larger databases are acceptable for
a single site repository, such as a
records center, but it is not suggested.
Site collec-
tions per
Content
Database
2,000 recom-
mended; 5,000
maximum
Content database limit This limit is based on how long it
takes to upgrade. Also, the more site
collections there are in a content data-
base, the smaller they should be.
WebSite 250,000 per site
collection
Site collection limits Note that creating many subsites
simultaneously may fail at this limit.
Sites have a way of increasing quietly;
it is easy to have more than you think.
Site
Collection
Size
100 GB per site
collection
Site collection limits Site collection size should never
exceed 100 GB unless it is the only site
collection in a content database.
Documents 30,000,000 per
library
List and library limit This value depends on how well you
organize the data in the library, using
folders, nested folders, and using
views.
626382c01.indd 38 1/27/11 10:47:26 AM