Microsoft Office Tutorials and References
In Depth Information
limit for each document, then that would be no more than 20 MB of indexed entries per
document and therefore (going with our scenario) about 400 MB stored in the search database for
that one document library.
When you’re deciding how much storage space your SharePoint server should use in SQL,
consider this:
You need to have an idea of what your users are going to do. Estimate how many
docu•u
ments they are going to be collaborating on and storing. Think about what lists they will be
using and how they will be used.
Plan how you are going to manage attachments and versioning.
•u
Plan how you are going to manage user websites—especially ones generated for document
•u
and meeting workspaces.
Plan on using site collection quota templates to keep site collection storage in check (in
•u
addition to limiting site collections per content database). Remember the Recycle Bins
as well. The end-user Recycle Bin contents at the site level are part of the site collection’s
quota, so keep an eye on it. But the second-stage, site-collection-level Recycle Bin can have
a quota that is a certain percentage of its site collection’s quota, but keep in mind that is in
addition to the site collection’s quota. That can cause an unexpected increase in storage
requirements if you aren’t prepared. Remember to empty your Recycle Bins to save space.
Also, on the SharePoint server, always leave some room for the paging file; try to go for at
•u
least the same amount as the server has in RAM.
Once you can estimate what you need, double that space. At least, always have 25 percent
more space than you expect to need. Always leave room to bloat. You will never go wrong.
It’s great if SharePoint works, but if you have no more room to store SharePoint’s data, the
users will be upset. There is a standard formula going around that might help in estimating for
user storage:
Database size = ((D × V) × S) + (10 KB × (L + (V × D)))
D = documents
S = average size of documents
L = list items (harder to average, but smaller; suggested three per document)
V = estimated number of versions
10 KB= constant (the estimated amount of metadata used by SharePoint)
So, in this case:
D = 200 yearly (that’s 20 documents and 10 pictures per document)
S = 10240 KB (that’s 10 MB per document/picture, in kilobytes)
L = 600 (rounding to three times the documents, a rule of thumb considering that there is
likely to be a couple discussion items and a calendar entry per document)
V = 7 (estimating the number of versions for the documents)
Search JabSto ::




Custom Search