- For a SharePoint content database up to 200 GB there are no special requirements and this limit is included for consistency.
- For a SharePoint content database up to 4 TB you need to additionally plan for the following two requirements:
- Requires disk sub-system performance of 0.25 IOPS per GB, 2 IOPS per GB is recommended for optimal performance.
- Requires the customer to have plans for high availability, disaster recovery, future capacity, and performance testing.
- For a SharePoint content database over 4TB specifically for a Document Archive scenario you are required to additionally plan for the following:
- SharePoint sites must be based on Document Center or Records Center site templates and must be an archive scenario where less than 5% of content is actively read from each month and less than 1% of content is actively written to.
- Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint objects in the content database. Note: document archive content databases can be the recipient of documents as a result of Content Routing workflow.
- Other specific limits changes being made at the same time:
- A new limit of 60million items in any one SharePoint content database
- The specific 5 TB limit per SQL Server instance has been removed. Instead you should work with a SQL Server professional to plan for database storage.
Monday, July 11, 2011
SharePoint 2010 - 4TBs databases SP1
With the release of SP1 SharePoint 2010 now supports up to 4TBs databases under specific circumstances liste below. Go to Link for more information.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment