|
Limit
|
Maximum value
|
Limit type
|
Notes
|
|
Content database
|
300 per Web application
|
Supported
|
With 300 content databases per Web application, end user operations such as navigating
to the site or site collections are not affected. But administrative operations
such as creating a new site collection will experience performance degradation.
We recommend that you use Windows® PowerShell™ to manage the Web application when
a large number of content databases are present, because the management interface
becomes slow and difficult to navigate.
|
|
Zone
|
5 per Web application
|
Boundary
|
The number of zones defined for a farm is hard coded to 5. Zones include Default,
Intranet, Extranet, Internet, and custom.
|
|
Managed path
|
20 per Web application
|
Supported
|
Managed paths are cached on the Web server, and CPU resources are used to process
incoming requests against the managed path list. If you plan to exceed twenty managed
paths in a given Web application, we recommend that you test for acceptable system
performance.
|
|
Limit
|
Maximum value
|
Limit type
|
Notes
|
|
Content database size
|
200 GB per Content database
|
Supported
|
We strongly recommended limiting 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.
|
|
Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS)
|
Time to first byte of any response from the NAS cannot exceed 20 milliseconds
|
Boundary
|
When SharePoint Server 2010 is configured to use RBS, and the BLOBs reside on NAS
storage, consider the following boundary. From the time that SharePoint Server 2010
requests a BLOB, until it receives the first byte from the NAS, no more than 20
milliseconds can pass.
|
|
Limit
|
Maximum value
|
Limit type
|
Notes
|
|
Web site
|
250,000 per site collection
|
Supported
|
The maximum recommended number of sites and subsites is 250,000 sites. You can create
a very large total number of Web sites by nesting subsites. For example, in a shallow
hierarchy with 100 sites, each with 1,000 subsites, you would have a total of 100,000
Web sites. Or a deep hierarchy with 100 sites, each with 10 subsite levels would
also contain a total of 100,000 Web sites. Note: Deleting or creating a site or
subsite can have significant impact on a site’s availability. Access to the site
and subsites will be limited while the site is being deleted. Attempting to create
many subsites concurrently may also fail.
|
|
Site collection size
|
100 GB per site collection
|
Supported
|
A site collection should not exceed 100 GB unless it is the only site collection
in the database. Certain site collection actions, such as site collection backup/restore
or Move-SPSite, cause large Microsoft SQL Server® operations which can have performance
impact or fail if other site collections are active in the same database.
|
|
Limit
|
Maximum value
|
Limit type
|
Notes
|
|
List row size
|
8,000 bytes per row
|
Boundary
|
For each SharePoint list or library item, it is only allowed to occupy 8000 bytes
in total in the database. 256 bytes are reserved for built-in SharePoint columns,
which leaves 7744 bytes for end-user columns. For details on how much space each
type of field consumes, please look at the Column Limits.
|
|
File size
|
2 GB
|
Boundary
|
The default maximum file size is 50 MB. This can be increased up to 2 GB, but a
large volume of very large files can impact farm’s performance.
|
|
Documents
|
30,000,000 per library
|
Supported
|
You can create very large document libraries by nesting folders, using standard
views and site hierarchy. This value may vary depending on how documents and folders
are organized, and by the type and size of documents stored.
|
|
Items
|
30,000,000 per list
|
Supported
|
You can create very large lists using standard views, site hierarchies, and metadata
navigation. This value may vary depending on the number of columns in the list and
the usage of the list.
|
|
Rows size limit
|
6 table rows internal to the database used for a list or library item
|
Supported
|
Specifies the maximum number of table rows internal to the database that can be
used for a list or library item. To accommodate wide lists with many columns, each
item may be wrapped over several internal table rows, up to six rows by default.
This is configurable by farm administrators through the object model only. The object
model method is SPWebApplication.MaxListItemRowStorage.
|
|
Bulk operations
|
100 items per bulk operation
|
Boundary
|
The user interface allows a maximum of 100 items to be selected for bulk operations.
|
|
List view lookup threshold
|
8 join operations per query
|
Threshold
|
Specifies the maximum number of joins allowed per query, such as those based on
lookup, person/group, or workflow status columns. If the query uses more than eight
joins, the operation is blocked. This does not apply to single item operations.
When using the maximal view via the object model (by not specifying any view fields),
SharePoint will return up to the first eight lookups.
|
|
List view threshold
|
5,000
|
Threshold
|
Specifies the maximum number of list or library items that a database operation,
such as a query, can process at one time, outside of the daily time window set by
the administrator during which queries are unrestricted.
|
|
List view threshold for auditors and administrators
|
20,000
|
Threshold
|
Specifies the maximum number of list or library items that a database operation,
such as a query, can process at one time when performed by an auditor or administrator
with appropriate permissions. This setting works in conjunction with Allow Object
Model Override.
|
|
Subsite
|
2,000 per site view
|
Threshold
|
The interface for enumerating subsites of a given Web site does not perform well
as the number of subsites surpasses 2,000. Similarly, the All Site Content page
and the Tree View Control performance will degrade significantly as the number of
subsites grows.
|
|
Coauthoring in Microsoft Word and Microsoft PowerPoint® for .docx, .pptx and .ppsx
files
|
10 simultaneous editors per document
|
Threshold
|
Recommended maximum number of simultaneous editors is 10. The boundary is 99.
If there are 99 co-authors who have a single document opened for simultaneous editing,
the 100th user and above will get a file in use error and have to view a read-only
copy.
More than 10 co-editors will lead to a gradually degraded user experience with more
conflicts and users will have to go through more iterations to get their changes
to upload successfully.
|
|
Limit
|
Maximum value
|
Limit type
|
Size per column
|
Notes
|
|
Single line of text
|
276
|
Threshold
|
28 bytes
|
SQL Server row wrapping occurs after each 64 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 384 Single line of text columns
per SharePoint list (6 * 64 = 384). However, because the limit per SharePoint list
item is 8000 bytes, of which 256 bytes are reserved for built-in SharePoint columns,
the actual limit should be 276 Single line of text columns.
|
|
Multiple Lines of Text
|
192
|
Threshold
|
28 bytes
|
SQL Server row wrapping occurs after each 32 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 192 Multiple lines of text columns
per SharePoint list (6 * 32 = 192).
|
|
Choice
|
276
|
Threshold
|
28 bytes
|
SQL Server row wrapping occurs after each 64 columns in a SharePoint list. The default
row wrapping value of 6 allows for a maximum of 384 Choice columns per SharePoint
list (6 * 64 = 384); ); however since the limit per SharePoint list item is 8000
bytes, of which 256 bytes are reserved for built-in SharePoint columns, the actual
limit should be 276 Single line of text columns.
|
|
Number
|
72
|
Threshold
|
12 bytes
|
SQL Server row wrapping occurs after each 12 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 72 Number columns per SharePoint
list (6 * 12 = 72).
|
|
Currency
|
72
|
Threshold
|
12 bytes
|
SQL Server row wrapping occurs after each 12 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 72 Currency columns per SharePoint
list (6 * 12 = 72).
|
|
Date and Time
|
48
|
Threshold
|
12 bytes
|
SQL Server row wrapping occurs after each eight columns in a SharePoint list. The
default row wrapping value of six allows for a maximum of 48 Date and Time columns
per SharePoint list (6 * 8 = 48).
|
|
Lookup
|
96
|
Threshold
|
4 bytes
|
SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 96 single value Lookup columns
per SharePoint list (6 * 16 = 96).
|
|
Yes / No
|
96
|
Threshold
|
5 bytes
|
SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 96 Yes / No columns per SharePoint
list (6 * 16 = 96).
|
|
Person or group
|
96
|
Threshold
|
4 bytes
|
SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 96 Person or Group columns per
SharePoint list (6 * 16 = 96).
|
|
Hyperlink or picture
|
138
|
Threshold
|
56 bytes
|
SQL Server row wrapping occurs after each 32 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 192 Hyperlink or Picture columns
per SharePoint list (6 * 32 = 192) ); however since the limit per SharePoint list
item is 8000 bytes, of which 256 bytes are reserved for built-in SharePoint columns,
the actual limit should be 138 Hyperlink or Picture columns.
|
|
Calculated
|
48
|
Threshold
|
28 bytes
|
SQL Server row wrapping occurs after each eight columns in a SharePoint list. The
default row wrapping value of six allows for a maximum of 48 Calculated columns
per SharePoint list (6 * 8 = 48).
|
|
GUID
|
6
|
Threshold
|
20 bytes
|
SQL Server row wrapping occurs after each column in a SharePoint list. The default
row wrapping value of six allows for a maximum of 6 GUID columns per SharePoint
list (6 * 1 = 6).
|
|
Int
|
96
|
Threshold
|
4 bytes
|
SQL Server row wrapping occurs after each 16 columns in a SharePoint list. The default
row wrapping value of six allows for a maximum of 96 Int columns per SharePoint
list (6 * 16 = 96).
|
|
Managed metadata
|
94
|
Threshold
|
40 bytes for the first, 32 bytes for each subsequent
|
The first Managed Metadata field added to a list gets four columns:
- A lookup field for the actual tag
- A hidden text field for the string value
- A lookup field for the catch all
- A lookup field for spillover of the catch all
Each subsequent Managed Metadata field added to a list adds two more columns
- A lookup field for the actual tag
- A hidden text field for the string value
The maximum number of columns of Managed Metadata is calculated as (14 + (16 * (n-1)))
where n is the row mapping value (default of 6).
|
|
Limit
|
Maximum value
|
Limit type
|
Notes
|
|
Number of SharePoint groups a user can belong to
|
5,000
|
Supported
|
This is not a hard limit but it is consistent with Active Directory® guidelines.
There are several things that affect this number:
- The size of the user token
- The groups cache: SharePoint Server 2010 has a table that caches the number of groups
a user belongs to as soon as those groups are used in access control lists (ACLs).
- The security check time: as the number of groups a user is a member of increases,
the time required for the access check increase as well.
|
|
Users in a site collection
|
2 million per site collection
|
Supported
|
You can add millions of people to your Web site by using Microsoft Windows® security
groups to manage security instead of using individual users.
This limit is based on manageability and ease of navigation in the user interface.
When you have many entries (security groups of users) in the site collection (more
than one thousand), you should use Windows PowerShell to manage users instead of
the UI. This will provide a better management experience.
|
|
Active Directory Principles/Users in a SharePoint group
|
5,000 per SharePoint group
|
Supported
|
SharePoint Server 2010 allows you to add users or Active Directory groups to a SharePoint
group.
Having up to 5,000 users (or Active Directory groups or users) in a SharePoint group
provides acceptable performance.
The activities most affected by this limit are:
- Fetching users to validate permissions. This operation takes incrementally longer
with growth in number of users in a group.
- Rendering the membership of the view. This operation will always require time.
|
|
SharePoint groups
|
10,000 per site collection
|
Supported
|
Above 10,000 groups, the time to execute operations is increased significantly.
This is especially true of adding a user to an existing group, creating a new group,
and rendering group views.
|
|
Security principal: size of the Security Scope
|
5,000 per Access Control List (ACL)
|
Supported
|
The size of the scope impacts the data used for a security check calculation. This
calculation occurs each time the scope changes. There is no hard limit, but the
bigger the scope, the longer the calculation takes.
|