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

New schema is the first choice, IMHO.

Give the new schema at least its own tablespace(s). Whenever there is a need for separate updates or recovery of a schema that will give you much more flexibility.

(At a relative new CT site I'm coping with a multi-multi GB dictionary managed USERS tablespace with 323 (merely identical) schema's stored in it. It's a real PITA to get everything sorted out, especially because it is a 24x7 ASP). The CTO is a brilliant developer, but a lousy DBA.

Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

On Wed, 2005-10-05 at 16:08 -0500, BP wrote:

> 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. Now...as 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
> --
> http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l