Re: Different databases or different schemas?

From: Chuck Whealton <>
Date: Tue, 24 Jun 2008 18:15:17 -0700 (PDT)
Message-ID: <>

On Jun 24, 11:55 am, wrote:
> Hi,
> Even if I'm using Oracle since some year, I have some (many?) doubts
> about the use of differents schema instead of different DBs.
> Generally to manage a test environment, a development enviroment and a
> production environment, I create 3 different databases on the same
> oracle instance (MYDB_TEST, MYDB_PROD, MYDB_DEV). But I was thinking
> if to create only 1 database and 3 different schemas for test,
> developing and production on the same database, could be a better
> solution.
> Does anybody can suggests me which is the best solution and which are
> the advantages (and disadvantages) of the two choices?
> Thank you in advance
> Alessandro Rossi


There's a number of legitimate ways to go about this.

At one clients facility, we would have separate systems with their own individual Oracle installations and databases on each one. Doing it this way, we we're also able to test out operating system patch sets with no repercussions to production.

That particular client is also in a regulated industry so they usually had separate production, pre-production, and development environments.

I'd probably think about having at least two separate systems - be they physical or virtual. That way, you can test both operating system and Oracle updates without affecting production. Just my own take on it.

Charles R. Whealton
Charles Whealton @ Received on Tue Jun 24 2008 - 20:15:17 CDT

Original text of this message