Re: More than one database on a system? Was: need advice on filesystem layout

Christian Pfundtner (Christian_Pfundtner_at_msn.com) wrote:
: mccurdy_at_ucsvax.sdsu.edu (Mike McCurdy) wrote:

: >This brings to mind a question that I have regarding several database
: >systems that I will be consolidating to one AIX box. Our plan is to create
: >one database and segregate the various applications by tablespace. Is
: >there any reason to use multiple databases instead of one?
 

: There are multible reasons for multible databases on one system:
 

: 1) if you are developing your own applications it is much easyer to
: use a PRODuction and a DEVelopment Database.
 

: 2) If you have different Appliactions which have nothing to do with
: the other, it will be easyer to administrate if they are in different
: databases.
: *) Upgrade one Application/DB will not desturbe the other Apps
: *) If the Appls are from different Vendors there will be no problem
: with secutiry and such things.
: *) Recovery of ONE Database, lets other DBs still work fine...

You can recover tablespaces individually, generally this is not an issue.

: 3) If you are a outsourcing company, you should use at least one
: database for each customer.

Totally agree, for large systems running under UNIX multiple machines may still be a better way to avoid one customer impacting another. It can be very easy for one application so exhast a global resource (IPC,memory etc).

: But there are also multibe reasons for using only ONE Database.
 

: 1) there is less overhead for multible SGA,...

I think you meant more overhead for multiple SGAs :-)

: 2) It is less DBA work if you only have to manage on DB

As I see it the main plus is one set of archives to manage, one set of backups to create...

[snip]

: regards
: chris

--
Peter Golledge