RSS Feed
LinkedIn
Delicious
Skip to main content

Cornelius J. van Dyk's SharePoint Brain Dump

Rate this blog:
Go Search
Home
Step-by-Step Guides
Downloads
Post Archive
Capacity Planning
Architecture & Topology
Support Forums
SharePoint Team Blog
  

 Important Posts

  Complete MOSS Licensing Info
  SharePoint Speak Terminology Dictionary
  SPCAP - SharePoint Capacity Planning Tool
  Step-by-Step – A REAL world upgrade of a SharePoint Portal Server 2003 (SPS) farm to Microsoft Office SharePoint Server 2007 (MOSS)
  Best Practice - Determine if a SPUser has Admin rights to the SPWeb
  SharePoint 2010 - Good, Better, Best
Cornelius J. van Dyk's SharePoint Brain Dump > Posts > What do I gain or lose by using SharePoint site collections rather than sub sites/webs?
What do I gain or lose by using SharePoint site collections rather than sub sites/webs?

Terry, asked in the forums what you gain and/or lose if you architect your sites around site collections rather than sub sites/webs. Here's my take on this issue:

If you use site collections you lose:

  1. Aggregation/rollups. Components such as the Content Query Web Part that can perform rollups of lists across entire site collections and thus sub sites, cannot roll up across multiple site collections. This can generally be offset by the use of the Data View Web Part, but you need SharePoint Designer to use that web part since it is not available through the UI.
  2. Peer site references. You can define columns to source their data from peer sites within the site collection, but not across site collections.

If you use site collections, you gain:

  1. Strict security isolation. For example, the creation of site security groups for each sub site, makes those site security groups visible to any administrator of any peer sub web within the site collection. In strict security context cases, the names of these groups, which usually involve the site name, could reveal the existence of some site that you might not want everyone to be aware of. It just helps to isolate security to the site level.
  2. Better backup granularization. Doing site collection backups can be much faster and more efficient when sites are broken into many site collections rather than one.
  3. Better stale site management. SharePoint's stale site management features are, as you might have guessed, tied to site collections. This means that if you have a site collection that contains 10 sites of which 9 are never used but one gets some usage, then that site collection, and the 90% stale content, never gets flagged for review.
  4. Better quota management. Quotas can be assigned at the site collection level. If the site collection contains multiple sub webs, it becomes harder to determine which site(s) are most active and consuming the majority of the allotted quota.

Later
C

Kick it Fave it Digg it Reddit Del.icio.us

Comments

http://www.sharepointblogs.com/joed

With site collections, you also lose integration of the site structure into the navigation from the top level site.  When you go to the site collection top level site, the navigation across the top changes to the site collection's structure.

But, related to the backup point, you can give a site collection its own content database.
at 4/17/2008 7:34 PM

http://www.cjvandyk.com/blog

Hey Joe,

You're partially correct on the top nav issue.  Since you can still manually manipulate the top menu (not available in 2003), I would consider it a workaround requirement rather than a total loss of functionality.  True it's not pretty, but you can manually create top nav links to your other site collections.

Later
C
Cornelius J. van Dyk at 4/20/2008 4:34 AM

http://sharepointxperience.blogspot.com

About the top nav navigation issue you could provide your web application with a custom navigation provider that makes all the work for you.
at 4/21/2008 1:39 AM

http://www.cjvandyk.com/blog

Hey SharePointXperience,

Good point...

Later
C
Cornelius J. van Dyk at 4/24/2008 2:57 AM

Add Comment

PLEASE NOTE
Comments are moderated so posting your comment here, will NOT make it visible right away.  Once I've reviewed your comment, I will publish it for all to see.  This is unfortunately needed in order to deal with all the crapware and spambots that post to my blog on a regular basis.

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.

Your Email or Blog URL *


Body *


Attachments