Microsoft Office Tutorials and References
In Depth Information
So the formula would be as follows:
((200 x 7) × 10240KB) + (10KB × (600 + (7 × 200))
or 14, 336,000 + 20,000 = 14,365,000KB
14,356,000KB is about 13.6909 GB (rounded up to 14)
This averages to a storage size of about 14 GB (estimating high of course) per year. Then you
need to factor in the storage space that Search will need (about 40 percent of the size of stored
files, or in the case of 14 GB, factor in an additional 5.6 GB).
Keep in mind that your environment may be different; after you install your SharePoint
server, make sure you monitor the activity. Create a test group that represents a small but
measurable sample of your expected users. See how many of them use the server, when they
use it, how they use it, and how much they store on the server. Then multiply the increase in
resources based on their activities by an estimate of how many more users will be doing the
same sorts of things when the server goes live. If you don’t think the suggested hardware
will be up to the task, improve it. Plan for at least 20 percent more growth than you expect—
just in case. It’s better to find out that your system is not adequate now than to find out when
everyone is using it.
Storage is well worth the price you pay for it (and is often inexpensive). Use RAID to make
your storage fault tolerant; mirror the web servers, and cluster your SQL servers if you can
(especially now that SharePoint is failover aware). If there is drive failure, you’ll be grateful
In addition to its hardware limitations, SharePoint has some software limitations. Microsoft
beat the heck out of some servers to see how they performed; and they found that when certain
objects reached a maximum number, performance degraded significantly. Previously, the list of
limitations for SharePoint was considered a guideline of acceptable performance. Now it is
considered software boundaries and limitations.
These boundaries and limitations come in three types:
Boundaries Hard limits that cannot be exceeded by design.
Thresholds Limits that have a default value for best performance, but that value can be
Supported Limits Recommended limits, based on testing. Surpassing these limits could
result in performance issues and possible “deleterious” effects.
Tables 1.1–1.3 list the object limitations you need to know. At this point, you may not really
realize the importance of some of these objects, but you will. It’s always good to know up
front what limitations there might be for something in case you might end up being
responsible for it. These are not the full and comprehensive tables (which are available on TechNet;
just search for SharePoint 2010 software boundaries and limitations ); they simply list the most
relevant to SharePoint Foundation in a standard installation. (Note that much of what is
available online is related to the SharePoint Server product more than SharePoint Foundation.)