Re: Seperate instances vs. seperate schemas

A related issue:

Upgrading a single instance may force applications to upgrade in tandem.

Al wrote:
>
> Combining two UNRELATED production databases in the same instance can cause
> you some grief in the event of a recovery. You may need to recover
> application A to a certain point in time (i.e restore and roll forward).
> However, this may impact application B, which could generate a political
> problem between your (two) sets of user communities.
>
> Tao36 <tao36_at_aol.com> wrote in article
> <19971205193300.OAA08814_at_ladder01.news.aol.com>...
> > I would like to get feedback from this group on the following:
> >
> > I am dba for a small software company. We currently have 2 products which
 run
> > on Oracle with Powerbuilder front-ends. The products are similar in that
 they
> > share some common table names and data.
> >
> > I currently have 4 seperate instances running..... a production and test
> > instance for each of the two products.
> >
> > The current debate between the developers and myself is whether these
 should
> > remain as seperate instances, or be combined into one instance as
 different
> > schemas. I don't believe either scenario is ideal, but am curious to hear
 the
> > thoughts of others on the subject.
> >
> > Thanks for any insight on this matter.
> >
> > Kevin
> >
  Received on Tue Dec 09 1997 - 00:00:00 CST