From oracle-l-bounce@freelists.org Wed Oct 5 18:39:05 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j95NcoJP014737 for ; Wed, 5 Oct 2005 18:39:00 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j95NchvX014727 for ; Wed, 5 Oct 2005 18:38:43 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 1DA3E1F3E03; Wed, 5 Oct 2005 18:37:58 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06365-06; Wed, 5 Oct 2005 18:37:58 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 8737A1F3E10; Wed, 5 Oct 2005 18:37:57 -0500 (EST) Subject: Re: Rule of thumb for new schema vs. new database? From: Carel-Jan Engel To: brian.peasey@gmail.com Cc: Oracle-L In-Reply-To: References: Content-Type: multipart/alternative; boundary="=-wnGzdPWgWdC4dYsCWyW9" Organization: DBA!ert Date: Thu, 06 Oct 2005 01:35:53 +0200 Message-Id: <1128555353.16212.6.camel@dbalert199.dbalert.nl> Mime-Version: 1.0 X-archive-position: 26435 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: cjpengel.dbalert@xs4all.nl Precedence: normal Reply-To: cjpengel.dbalert@xs4all.nl X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-mailscan-MailScanner-Information: Please contact the ISP for more information X-mailscan-MailScanner: Found to be clean X-MailScanner-From: oracle-l-bounce@freelists.org X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Level: X-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE autolearn=ham version=2.63 --=-wnGzdPWgWdC4dYsCWyW9 Content-Type: text/plain Content-Transfer-Encoding: 7bit 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 --=-wnGzdPWgWdC4dYsCWyW9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit 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

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