Limit
|
Maximum
value
|
Limit
type
|
Notes
|
List row size
|
8,000 bytes per row
|
Boundary
|
Each list or library item can only
occupy 8,000 bytes in total in the database. 256 bytes are reserved for
built-in columns, which leaves 7,744 bytes for end-user columns. For details
on how much space each kind of field consumes,
|
File size
|
2 GB
|
Boundary
|
The default maximum file size is 250
MB. This is a configurable limit that can be increased up to 2 GB (2,047 MB).
However, a large volume of very large files can affect farm performance.
|
Documents
|
30,000,000 per library
|
Supported
|
You can create very large document
libraries by nesting folders, or 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.
|
Major versions
|
400,000
|
Supported
|
If you exceed this limit, basic
file operations—such as file open or save, delete, and viewing the version
history— may not succeed.
|
Minor versions
|
511
|
Boundary
|
The maximum number of minor file
versions is 511. This limit cannot be exceeded.
|
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 the same time outside 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 the same time when they are performed by an auditor or administrator with
appropriate permissions. This setting works 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 decrease significantly as the number of subsites
grows.
|
Coauthoring in Word and PowerPoint
for .docx, .pptx and .ppsx files
|
10 concurrent editors per document
|
Threshold
|
Recommended maximum number of
concurrent editors is 10. The boundary is 99.
If there are 99 co-authors who
have a single document opened for concurrent editing, each successive user
sees a "File in use" error, and can only open a read-only copy.
More than 10 co-editors will lead
to a gradually degraded user experience with more conflicts, and users might
have to go through more iterations to successfully upload their changes to
the server.
|
Security scope
|
50,000 per list
|
Threshold
|
The maximum number of unique
security scopes set for a list cannot exceed 50,000.
For most farms, we recommend that
you consider lowering this limit to 5,000 unique scopes. For large lists,
consider using a design that uses as few unique permissions as possible.
When the number of unique security
scopes for a list exceeds the value of the list view threshold (set by
default at 5,000 list items), additional SQL Server round trips take place
when the list is viewed, which can adversely affect list view performance.
A scope is the security boundary
for a securable object and any of its children that do not have a separate
security boundary defined. A scope contains an Access Control List (ACL), but
unlike NTFS ACLs, a scope can include security principals that are specific
to SharePoint Server 2013. The members of an ACL for a scope can include
Windows users, user accounts other than Windows users (such as forms-based
accounts), Active Directory groups, or SharePoint groups.
|
Tuesday, September 15, 2015
List and library limits in SharePoint 2013
Subscribe to:
Post Comments (Atom)
What is the cost of migration to SharePoint 2016?
Below are the points to understand better how much the cost of migration to SharePoint 2016 could be for your organization: What ver...
-
Built-in URL Filtering SharePoint’s list view controls ( XsltListViewWebPart , ListViewWebPart , etc) recognize a number of parameters ...
-
We can filter a list using query parameters and the result will be displayed in list view, So we need a SharePoint list view for the same. ...
-
Introduction SharePoint 2013 (and previous versions) uses a client side “token” to validate posts back to SharePoint to prevent attacks w...
No comments:
Post a Comment