MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS Architecture

  Asked By: Ashu    Date: Aug 11    Category: MOSS    Views: 657

I'm about to roll out a MOSS environment for my enterprise.

We have 12 functional areas. These sites will begin small (ie: not
where near the 100 GB (soft) limit for content DBs). I'm thinking about
running all sites under a single web application, using a separate site
collection for each functional area.

I'm also considering using a separate content database for each site

Thoughts? Is this total overkill or intelligent design?



1 Answer Found

Answer #1    Answered By: Kalash Karmakar     Answered On: Aug 11

I think great for backup and other infrastructure considerations, but I would be
concerned about the ways in which it would limit your ability to make use of
consistency strategies across your organization.

You don't say much about your organization or the needs that drove you to this
design, so I may be way off, but my initial concern would be that using separate
site collections for functional areas  will cause you to either avoid using
shared content types, templates, web parts, site templates, site columns,
taxonomy, etc. between functional areas, or force you to do a lot of work to
duplicate those shared factors, and will lead to the tendency to them getting
inconsistent. Remember that the site collection is the unit of shared taxonomy.
I generally would use separate site collections when people specifically *don't*
want to share categories, workflows, templates, web parts, customizations, etc.,
between organizations using SharePoint.

Didn't find what you were looking for? Find more on MOSS Architecture Or get search suggestion and latest updates.