Capacity Planning for My Sites
My Sites are individual site collections,
supporting document libraries, lists, and subsites. By default, the
owner of a My Site has full control over the collection, and carte
blanche on what he or she may store in the collection. This suggests
that the size of the default content database for the My Site Host
application may grow quite large, as the number of users in an
organization (with a My Site) grows. Furthermore, SharePoint provides
incentive for users to store content and track events in their My Site,
thus increasing user adoption and the need for better capacity planning.
It is good practice to ensure portability of
the content databases and dispersal of My Sites across many content
databases in the host application. Since each
user’s My Site is a site collection, you need to make sure that as more
users sign up for My Site space, SharePoint ensures creation of new
content databases as the number of site collections grow.
How many content databases do you need, and
what limit should you set for the number of My Site collections per
database? This depends on the expected amount of content in each My
Site (site collection). Microsoft now allows database sizes up to four
terabytes, and this limit will grow in the future. Depending on your
need for portability and desire for smaller database sizes, the number
of site collections in a given database and the expected size of these
site collections will roughly define the size of your database. Quota
management (see the settings of the My Site Host web application, in
the web application list) will allow administrators to restrict the
amount of content that users upload to their personal My Sites. If you
have the luxury of multiple SQL Servers, you may decide to host My Site
content databases on a different server from other areas in your
SharePoint farm. The following steps demonstrate restricting My Site
collections in a content database to 50 instances:
- Open Central Administration.
- Click the Application Management link.
- Click the Manage Content Databases link.
- Select the content database for the My Site Host application.
- In the Database Capacity Settings section, change the maximum
number of sites to 50, and set the warning 10% less (45). This ensures
that the administrators receive a warning when the number of sites in
the current content database grows to 45 and when at 50 SharePoint will
create a new content database.
A Tour of SharePoint 2013 My Sites
My Sites in SharePoint 2013 have a new look
and feel compared to those of the previous version. Like the rest of
the user interface of SharePoint 2013, Microsoft redesigned the look
and feel of user profile information and My Sites for a more social
immersive experience. In previous versions of SharePoint, the My Site
was clunky and often perceived as an afterthought, and interrupted the
flow of the user interface. Even SharePoint 2010 had issues with the
clear delineation of My Content and My Profile in the top My Site
navigation.
With My Site capability enabled in the farm,
users now see a pervasive set of links at the top right of the page;
these links link to the current user’s newsfeed, favorite sites, and SkyDrive location in My Site. Figure 2 shows an image of the standard team site
in my development environment. Because I have My Sites enabled, I see
the Newsfeed, SkyDrive, and Sites links at the top right. No matter
what page I visit in the site, I always see these links.
The familiar display name of the current user
also displays in the top right, and irrespective of whether you have
enabled My Sites, clicking the name and selecting the “About Me” menu
option will display a profile page of the current logged on user. This
is an important distinction—in the past I have witnessed confusion
among users of SharePoint who believed you had to enable My Sites to
take advantage of user profiles and user profile management in a
SharePoint farm.
Note User profiles and profile editing operate independent of My Sites, but inclusion of My Site enhances the social experience for users.