Limiti raccomandati per Sharepoint Services 3.0
La tabella sottostante riporta i limiti consigliati per un'infrastruttura basata su Windows Sharepoint Services 3.0 .
Tali valori per alcune voci "potrebbero" essere superati, ma quasi certamente si andrebbe incontro ad un notevole degrado delle prestazioni dell'intero ambiente Sharepoint.
| Site object | Guidelines for acceptable performance | Notes | Scope of impact when performance degrades |
| Site collection | 50,000 per content database | Total farm throughput degrades as the number of site collections increases. | Farm |
| Site collection | 150,000 per Web application | This limit is theoretical, and is dependent largely upon: · Performance of the database server on which the configuration database resides. · Performance of the Web servers in the farm. · Network bandwidth between the Web servers and the database server. | This is not a hard limit, and assumes a single database server. Your environment may not be able to host this many site collections per Web application. Distributing content databases across additional database servers can increase the effective limit of the number of site collections per Web application. You should perform testing to determine the actual effective limit in your environment. | Farm |
| Web site | 250,000 per site collection | You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites. | Site collection | |
| Subsite | 2,000 per Web site | The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. | Site view | |
| Document | 5 million per library | 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. | Library | |
| Item | 2,000 per view | Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance. | List view | |
| Document file size | 50MB (2GB max*) | File save performance is proportional to the size of the file. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB. | Library, file save performance | |
| List | 2,000 per Web site | Testing indicates a reduction in list view performance beyond two thousand entries. | List view | |
| Field type | 256 per list | This is not a hard limit, but you might experience list view performance degradation as the number of field types in a list increases. | List view | |
| Column | 2,000 per document library 4,096 per list | This is not a hard limit, but you might experience library and list view performance degradation as the number of columns in a document library or list increases. | Library and list view | |
| Web Part | 50 per page | This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected. | Page | |
L'articolo completo a cui fare riferimento (che contiene tra l'altro informazioni molti utili relative alle utenze, l'hardware e il carico di rete) è reperibile all'indirizzo qui di seguito:
Plan for software boundaries (Windows SharePoint Services):
http://technet.microsoft.com/en-us/library/cc287790.aspx
