| 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, see Column limits.
|
File size
|
2 GB
|
Boundary
|
The default maximum file size is 50 MB. This can be increased up to 2 GB, 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.
|
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 Microsoft Word and Microsoft 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, any user after the 100th user sees 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.
|
Security scope
|
1,000 per list
|
Threshold
|
The maximum number of unique security scopes set for a list should not exceed 1,000.
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. 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.
|
10 January, 2012
List and library limits:SharePoint 2010
List of all SharePoint 2010 and Office Server 2010 SP1 packages
All SP1 packages are available for download from Microsoft Download Center. You can download and install the following service packs for each product that you have installed.
| Package name | How to obtain the package | Knowledge Base article |
|---|---|---|
| Microsoft SharePoint Server 2010 Service Pack 1 |  |
2460045 Description of SharePoint Server 2010 SP1
|
| Microsoft SharePoint and Project Server 2010 Service Pack 1 | |
2460047 Description of Project Server 2010 SP1
|
| Microsoft Office Web Apps Service Pack 1 | |
2460073 Description of Office Web Apps SP1
|
| Microsoft Search Server 2010 Service Pack 1 | |
2460070 Description of Search Server 2010 SP1
|
| Microsoft FAST Search Server 2010 for SharePoint Service Pack 1 | |
2460039 Description of FAST Search Server 2010 for SharePoint SP1
|
| Microsoft Groove Server 2010 Service Pack 1 | |
2460067 Description of Groove Server 2010 SP1
|
| Microsoft 2010 Server Language Pack Service Pack 1 | |
2460056 Description of Office Servers 2010 Language Pack SP1
|
| Microsoft SharePoint Foundation 2010 Service Pack 1 | |
2460058 Description of SharePoint Foundation 2010 SP1
|
| Microsoft SharePoint Foundation 2010 Language Pack Service Pack 1 | |
2460059 Description of SharePoint Foundation 2010 Language Pack SP1
|
| Microsoft SharePoint 2010 Indexing Connector for Documentum Service Pack 1 | |
2460054 Description of SharePoint 2010 Indexing Connector for Documentum SP1
|
Workflows in SharePoint Server 2010
Microsoft has published an awesome information about workflows which are present in SharePoint Server 2010
- Contract approval Guiding a proposed contract among members of an organization who must approve or reject it.
- Expense reporting Managing the submission of an expense report and associated receipts, reviewing the report, approving it, and reimbursing the submitter.
- Technical support Guiding the progress of a technical support incident as it is opened by a customer, investigated by a support engineer, routed to technical experts, resolved, and added to a knowledge base.
- Interviewing Managing the process of interviewing a job candidate. This includes scheduling and tracking interview appointments, collecting interview feedback as it accumulates, making that feedback available to subsequent interviewers, and facilitating the hire/no-hire decision.
- Content publishing Managing the approval of the publication of content on the Internet presence site of an enterprise.
Automating business processes
Businesses depend on business processes. Although those processes often involve software, the most important processes in many organizations depend on people. Workflows can automate interactions among the people who participate in a process to improve how that process functions, increase its efficiency, and lower its error rate.
Many processes can benefit from automated support for human interactions. Examples include the following:
- Approval A common aspect of human-oriented business processes is the requirement to get approval from multiple participants. What is being approved can vary widely, ranging from a Microsoft Word document that contains next year’s marketing plan to an expense report from a trip to a conference. In every case, some number of people must review the information, perhaps appending comments, and then indicate approval or rejection.
- Coordinating group efforts Whether it is preparing a response to a request for proposal (RFP), managing the translation of a document into one or more languages, or something else, many processes require people to work together in an organized way. By defining the steps of the process through an automated workflow, the group’s work can be made more efficient and the process itself more predictable.
- Issue tracking Many business processes generate a list of outstanding issues. An automated workflow can be used to maintain that list, assign issues to the people who can resolve them, and track the status of that resolution.
Predefined workflows
Microsoft SharePoint Server 2010 includes the following predefined workflow templates that address common business scenarios:
- Collect Feedback Routes a document or item to a group of people for feedback. Reviewers can provide feedback, which is then compiled and sent to the person who initiated the workflow. By default, the Collect Feedback workflow is associated with the Document content type, and therefore it is automatically available in document libraries.
- Approval Routes a document or item to a group of people for approval. By default, the Approval workflow is associated with the Document content type, and therefore it is automatically available in document libraries. A version of the Approval workflow is also associated by default with the Pages library on a publishing site, and can be used to manage the approval process for the publication of Web pages.
The Approval workflow is a staged approval model (that is, the first set of approvers can undergo the review and approval process, then the next set of approvers, and so on). Each stage or approval set can also have its own behavior. For example, members of the first group of approvers can do their review in serial approval order (one after the other), members of the second group can do their review in parallel (reviewers can provide feedback in any order), and so on. - Disposition Approval Manages document expiration and retention by letting participants to decide whether to keep or delete expired documents. The Disposition Approval workflow supports record management processes and is intended for use primarily in a Records Center site.
- Collect Signatures Routes a document that was created in a Microsoft application to a group of people to collect their digital signatures. This workflow must be started in applications in the 2007 Microsoft Office system and the Microsoft Office 2010 suites such as Microsoft Word. Participants must complete their signature tasks by adding their digital signatures to the documents in the relevant client program. By default, the Collect Signatures workflow is associated with the Document content type, and therefore is automatically available in document libraries. However, the Collect Signatures workflow appears for a document in the document library only if that document contains one or more Microsoft Office Signature Lines.
- Three-state Designed to track the status of a list item through three states (phases). It can be used to manage business processes that require organizations to track a high volume of issues or items, such as customer support issues, sales leads, or project tasks.
The Three-state workflow is so named because it tracks the status of an issue or item through three different states, and through two transitions between the states. For example, when a workflow is initiated on an issue in an Issues list, SharePoint Server 2010 creates a task for the assigned user. When the user completes the task, the workflow changes from its initial state (Active) to its middle state (Resolved) and creates a task for the assigned user. When the user completes the task, the workflow changes from its middle state (Resolved) to its final state (Closed), and creates another task for the user to whom the workflow is assigned at that time. Note that this workflow is only supported on lists, not libraries. - Translation Management Manages manual document translation by creating copies of the document to be translated and by assigning translation tasks to translators. This workflow is available only for Translation Management libraries.
- Issue Tracking Routes an issue to team members for resolution. It presents a Web page to the user who makes possible the entry of new issues; for example, customer complaints. As an issue progresses though different workflow states, the Web page of the user changes to reflect appropriate events; for example, a Web page that was closed when an issue is resolved.
Workflow associations
| Associate workflow with | Minimum permissions required |
|---|---|
List or library
|
Full Control permission level on the list or library
|
List or library content type
|
Member of the Site Owners group on the SharePoint site
|
Site content type
|
Member of the Site Owners group on the SharePoint site
|
Site
|
Member of the Site Owners group on the SharePoint site
|
Subscribe to:
Posts (Atom)