[support] Multi Site Question . . .

[Aaron Green]

Thanks for that link, and if this is hijacking this thread, I
apologize.  The situation described is a lot like mine, the one thing
I never saw answered was updating all databases during an upgrade if
your using separate databases and one multi-site installation.  Any
ideas there?

On 11/10/06, Paul Rooney <paul at f5sitedesign.com> wrote:
> Bryght is running over 1000 sites off of one code
> base:http://drupal.org/node/72328#comment-134751
>
> Paul
>
> Aaron Green wrote:
> > I'm wondering how high Drupal can go.  I am reviewing it for an
> > installation where it could be installed on 140 sites (departments
> > within a company).  I really can't afford to get to some odd number
> > and see serious performance issues.  The traffic most likely won't be
> > an issue, but huge amounts of content will go in the database.
> > Upgrading all of these as separate sites would be a nightmare, so
> > multi-site is my only solution at this time.
> >
> > On 11/10/06, Greg Knaddison - GVS <Greg at growingventuresolutions.com> wrote:
> >> On 11/10/06, Michelle Cox <mcox at charter.net> wrote:
> >>> The only real advantage I've found to multi site is security updates only
> >>> need to be applied in one place. I'm not sure that benefit outweighs the
> >>> pain of being forced to upgrade all sites at once.
> >> I agree and would just point out that for me, at 3 sites I said "why
> >> bother with multisite, it's not worth it" and then at 10 sites I said
> >> "security and general updates suck, I need multisite".
> >>
> >> So, there are different strategies for different situations.  If you
> >> have or are going to have lots of sites, multisite becomes a smart
> >> decision.
> >>
> >> Greg
> >> --
> >> [ Drupal support list | http://lists.drupal.org/ ]
> >>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>


-- 
Aaron Green
Web Content Coordinator
University of Southern Mississippi