Re: same application on multiple schemas
From: Jeremy <jeremy0505_at_gmail.com>
Date: Fri, 10 Apr 2009 17:58:43 +0100
Message-ID: <MPG.24498b1e601f103f989708_at_News.Individual.NET>
In article <M7IDl.4500$im1.4076_at_nlpi061.nbdc.sbc.com>, maustin_at_firstdbasource.com says...>
> Alberto wrote:
> > Hello, I'm designing a new big application.
> >
> > The application will be instantiated for multiple users. Each
> > application must have its own "database", or schema, Oracle speaking.
> >
>
> How many users per schema? This "scheme" sounds like a disaster waiting
> to happen. Do they need separate schemas or do they need separate
> databases instances?
>
>
Date: Fri, 10 Apr 2009 17:58:43 +0100
Message-ID: <MPG.24498b1e601f103f989708_at_News.Individual.NET>
In article <M7IDl.4500$im1.4076_at_nlpi061.nbdc.sbc.com>, maustin_at_firstdbasource.com says...>
> Alberto wrote:
> > Hello, I'm designing a new big application.
> >
> > The application will be instantiated for multiple users. Each
> > application must have its own "database", or schema, Oracle speaking.
> >
>
> How many users per schema? This "scheme" sounds like a disaster waiting
> to happen. Do they need separate schemas or do they need separate
> databases instances?
>
>
Why should it be a disaster waiting to happen? Suppose you were providing and appplication for multiple customers on a single database. And suppose one of those customers used the system far more heavily than other customers and it was decided to separate that user on its own database or server? Having a schema per customer then makes it easy to move it to another location. Another valid scenario might be that the customer starts off with the system hosted by a supplier but wishes an option to host on its own environment down the line.
-- jeremyReceived on Fri Apr 10 2009 - 11:58:43 CDT