Microsoft Office Tutorials and References
In Depth Information
Creating a quota
For my example, I am going to create a quota for site collections meant to contain blogs. Later
in the chapter, I will provide a web application for blogging site collections, and it would be nice
to have a storage quota for them.
Name the quota by entering it in the New Template Name field; mine uses Blog Quota . For
the quota limits, set the limit to 200 MB, with a warning at 150 MB.
The third section on this page lets you set a quota for any sandboxed solutions that might
be installed in the site collection. Sandboxed solutions are custom code solutions that can be
installed into a site collection directly, without farm access, and are restricted from making any
changes or accessing the rest of the farm. Typically, these are provided by third-party
developers, and what kind of quota (if any) they need varies dramatically (the default is 300 points, and
points are a combination of server resources like CPU cycles, or memory consumed). For this
example, we’re not dealing with any sandboxed solutions.
You can edit existing quota templates on this page, delete a template, and create a new
template based on an existing one (keep in mind that those edit and delete options won’t be
available if you don’t have an existing template in the farm yet). Although quota templates are meant
to be applied to site collections, they are actually available farm-wide.
Site Quotas and Locks
To assign a quota to an existing site collection, to check the current storage used, or to lock
the site collection, click Configure Quotas And Locks in the Site Collections section of the
Application Management page. This will take you to the page shown in Figure 10.21. In my
example, I am setting an individual quota on the London office site collection of 1024 MBs with
a notification email to be sent out when the site collection reaches 800 MBs, with a quota on the
sandboxed solutions of 300 points with a notification at 100.