Re: Seperate instances vs. seperate schemas

Just my opinion.....

Since you are a software company, I would assume that you would want your TEST and PROD to be able to reside on separate versions of Oracle which means separate instances. Thus you can test out new Oracle versions using the TEST version of your software. I would keep the two software products in the same instance with different schemas unless there is some overwhelming factor that requires you have 4 instances as you do now. As you know, each instance means more resources and management required.

-- 
Thomas W. Vanya
Oracle and OracleRdb Database Administrator
Eastman Chemical Company
-------------------------------------------------------------------------
(Due to proliferation of spammers, remove nospam from address.)

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

>