Re: When would you ever need two databases on one machine?

We run many servers with one or two test instances and a production instance on the same machine. I also have another server that has four instances running for four different 3rd party apps. Each instance is too small to warrant it's own server. We could have combined the four instances into one for easier managability but we made a conscious choice not to do that. This way, when one application is having problems, it doesn't affect the other apps (on the db side). Also, some 3rd party app upgrades can make significant changes to the db. Having it's own instance eases upgrading.

HTH,
Brian

Ray Cordoni wrote:
>
> How about where you have a production database and a test database and
> you want to keep everything except the database name exactly the same
> - same tables, same tablespaces, same schema owner, etc, etc. This
> makes setting up test databases relatively easy. It also makes it
> easy to move databases from one server to another and to size init.ora
> parameters to the needs of each specific database. This, by the way,
> is the preferred way to set up multiple Peoplesoft databases.
>
> On Tue, 4 Jan 2000 20:04:42 -0500, "Brad Czika"
> <bczika_at_mindspring.com> wrote:
>
> >I can't find it anywhere but there must be a good reason. Isn't it enough to
> >just have several tablespaces in the same database?
> >
> >Thanks,
> >Brad
> >
Received on Wed Jan 05 2000 - 07:59:06 CST