Using Multiple Databases

• Quoting Bpearc1_at_Tisdec.Tis.Tandy.Com to All dated 03-09-94 ***
  > Optimally, what we would like to do is to create a seperate database
  > for the new system and its required subsystems, but that has never been done
  > at our site.
  

Are you talking about running two separate instances of the database engine? On two separate machines, this makes sense, but may not make sense on the same machine...

> 3. What are the effects on the existing programs that are already >

      connecting to the existing database using '/' and not > specifying an "AT" in the "CONNECT"?

That's what the LOCAL parameter is for...
> 4. What will be the effects on the Oracle Tools (SQL*Forms, etc.)?

None whatsoever, except, of course, for the choice of database instances...
> 5. Would a single program, form, etc. be able to access both >
 databases at the same time?

Ah... Now if this is at all planned, you may want to seriously rethink running two instances of the database engine. Database links are nice, but joining data across instances cannot ever be as clean as joining data within the same instance.
> 6. What other effects (positive or negative) might this have?

Negative: if you ever want to share data, you are causing yourself needless overhead and maintenance headaches for no reason. There is virtually nothing you can accomplish in two instances of the database engine that you cannot accomplish in a single instance, but there are a lot of performance and maintenance issues which you are setting yourself up for.

Positive: it will be easier to move the separate databases onto separate machines later if you deal with all the aggravation up front. You can have two separate system administrators each doing more work than either would do alone. Received on Sat Mar 12 1994 - 01:06:00 CET