Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: New Schema or New Database?

RE: New Schema or New Database?

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Tue, 21 Jan 2003 07:50:04 -0800
Message-ID: <F001.00535F73.20030121075004@fatcity.com>


Glenn

   Creating a new database definitely costs more in support. It needs a backup plan, recovery testing, etc.

   In the past I've examined issues like how much the new application is like existing applications, whether it is likely to need the same upgrade timing, backup schedule (before RMAN).

   Lately my boss has started asking about how many databases a DBA can manage, so from now on, each schema gets its own database. Gotta get my numbers up!

Dennis Williams
DBA, 40%OCP
Lifetouch, Inc.
dwilliams_at_lifetouch.com

-----Original Message-----
Sent: Tuesday, January 21, 2003 8:54 AM
To: Multiple recipients of list ORACLE-L

Our DBA group has recently been getting numerous requests for new databases (training, inventory, customer contacts, etc..) from different departments within the company. Our normal procedure is to create a new instance for the database, create the schema, users, etc..., set up backups and turn it over. However, with the volume of requests we are now getting, we are pondering the idea of creating just one instance and giving each database request its own tablespace and schema. (similar to informix and sybase architecture).

My questions for discussion are these; 1) What are the benefits/risks associated with this scenario? Please note that these databases/schemas are unrelated. 2) What questions (for a user questionaire) should we ask regarding their database requirements, which will help us make an informed decision? My concerns are; 1) the inability to tune the instance for one schema/applications performance needs. 2) uptime/availability requirements may differ among the databases. 3) backup/restore scenarios specific to the schema/database (restore just one schema to a point-in-time).

We want to be able to save on memory(sga) and processes by combining the databases into one instance as schemas, but don't want to limit the different applications to 'one-size-fits-all' for performance/recovery scenarios. Any advice would be greatly welcomed.

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Glenn Travis
  INET: Glenn.Travis_at_sas.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: DENNIS WILLIAMS
  INET: DWILLIAMS_at_LIFETOUCH.COM
Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue Jan 21 2003 - 09:50:04 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US