Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Rule of thumb for new schema vs. new database?

Re: Rule of thumb for new schema vs. new database?

From: Alex Gorbachev <>
Date: Sun, 9 Oct 2005 12:12:57 +0200
Message-ID: <>


You can consider transportable tablespaces to move your schemas to a new 10g database providing they are separated on tablespace level. In our environment sometimes we are doing database upgrade in such a way - we have only 15 min quarterly outage window and no time for 30 min action with catpatch and etc. TTS allows us to upgrade it within 10-15 minutes. Coupling it with physical standby and plugging tablespaces from there we have excellent fallback option.

In our shop we first suppose to have separate database as our ultimate target is availability. Most of our applications are fast evolving and can sometimes influence the whole instance after loading new version. So rule of thumb for us divide and rule. So only after that we consider possibility to put new application/schema into any of existing databases. So our criteria - availability, criticality, recovery requirements, requirements for standby database, RAC needs, etc.

2005/10/6, Mercadante, Thomas F (LABOR) <>:
> Brian,
> Something that was not mentioned by everyone and what I think is the
> most important question to ask has to do with recoverability.
> If you need to roll one schema back for a data recovery reason, then the
> planning takes on another whole level of thought. In my mind, doing
> individual tablespace recoveries for this reason (if you separating each
> schema into separate tablespaces) is just not worth it. I prefer
> creating a new database instance on the same machine. Also, if these
> are canned applications separate instances gives you more flexibility if
> these applications are tied to specific release levels of Oracle. Right
> now I am unable to move to Oracle 10g for some of our databases because
> our current level of Curam (our current software du jour) is not
> certified against it. But we have other applications that can move to
> 10g.
> To me, it is not a big deal to create another instance. Sure it
> consumes more hardware resources, but it makes recovery a lot easier.
> Tom
> -----Original Message-----
> From:
> [] On Behalf Of BP
> Sent: Wednesday, October 05, 2005 5:09 PM
> To: Oracle-L
> Subject: Rule of thumb for new schema vs. new database?
> Hi Again,
> I have a meeting tomorrow with one of our project managers who is
> going to request a new schema or database. He wants my advice on which
> is best for his needs. I've said before I'm a neophyte DBA
> and do know the difference between a schema and a new database. I'm
> inclined to suggest just a new schema, but now I'm wondering to myself
> what kind of 'rule of thumb' is there is for this kind of decision.
> When would it be preferable to create a new db vs. just a schema in an
> existing db?
> Thanks for you help.
> Brian Peasey
> --
> --

Best regards,
Alex Gorbachev
Received on Sun Oct 09 2005 - 05:14:59 CDT

Original text of this message