Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 20. This course is intended for IT Professionals who use Microsoft SharePoint 2010 in a team-based, medium-sized to large environment. While they may have implemented a SharePoint deployment, they have limited experience in designing a SharePoint infrastructure. They likely work as a senior administrator who acts as a technical lead over a team of administrators. Members of this audience should have at least 6 months experience with SharePoint 2010. | Planning for Performance and Capacity 3-57 Database Size guideline Read write characteristics Description State 1 GB-1 terabyte Variable This database stores temporary state information for InfoPath Forms Service instances the chart Web Part and Visio Service instances. Note The read write characteristics of the database should influence your decision about storage in areas such as RAID configuration. Different physical disk types and different RAID configurations can provide different read and write performance. For example RAID 5 typically has poor write performance when compared with RAID 1. Question Which RAID type is typically recommended for transaction log storage of SQL Server databases Additional Reading For more information about database types and descriptions in SharePoint 2010 see http go.microsoft.com fwlink LinkID 200862 clcid 0x409. MCT USE ONLY. STUDENT USE PROHIBITED 3-58 Designing a Microsoft SharePoint 2010 Infrastructure Designing Capacity for Content Databases Key Points The following process describes how to estimate the storage that you require for content databases without considering log files 1. Calculate the expected number of documents. D represents this value in the formula at the end of this list. 2. Estimate the average size of the documents that you will be storing. 5 represents this value in the formula at the end of this list. 3. Estimate the number of list items in the environment. L represents this value in the formula at the end of this list. List items can be more difficult to estimate than documents particularly if there is no existing SharePoint 2010 implementation to base this on. As a general guideline estimate three times the number of documents. 4. Determine the approximate number of versions. Estimate the average number of versions that any document in a library will have. V represents this value in the formula at the end of this list. The value of V must be at least 1 for a single current version . MCT USE ONLY. .
