RE: Development projects: Multiple databases v/s multiple schemas

[Naveen Nahata]

Title: RE: Development projects: Multiple databases v/s multiple schemas

Thanx Raj and Bahar,

 

Raj I think you misunderstood my question. Or I might be misunderstanding a part of your reply :-)

 

I'll try to make my question clearer....

 

All the developers of a project work on the same DB(developers don't have individual DBs, project teams have). Different projects have individual servers running separate DBs on separate machines. This causes maintenance problems since currently project teams are responsible for their respective servers and they don't have the required expertize to do it.

 

We are planning to centralize the same and have one high-end machine running different versions of Oracle. My question is, for multiple projects which plan development on the same version of oracle, should I have 1 DB per project or within one DB multiple schemas for different projects?

 

The project teams want separate DBs because they think they can shutdown and startup the DB as per their wish. For them if something gets stuck, the best way is to restart the DB :-). But my point is that starting and shutting down a DB is not required at all, since most of the things can be dynamically changed.

 

The only thing is that certain init.ora parameters which cannot be changed dynamically. But since there is not too much of benchmarking done by the project teams the need to change init.ora parameters is not there.

 

If required this can be done in a separate test DB which will be allotted for testing and taken back once load testing/benchmarking is over.

 

The only problem I envisage with having multiple schemas is the name conflict between applications(projects) (2 applications might want to have schema with the same name).

 

I think the "stats" referred by Bahar are system level statistics like CPU utilization, waits etc. which I think are most relevant when doing tuning during load testing / benchmarking which as mentioned above can be done on a separate test DB specifically allotted for the same on a short term basis.

 

Regards

Naveen

 

-----Original Message-----
From: Jamadagni, Rajendra [mailto:[EMAIL PROTECTED]
Sent: Friday, June 20, 2003 7:35 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Development projects: Multiple databases v/s multiple schemas

if your schema will be cross-referencing, I vote for ONE db with multiple schema. This way, any changes in one schema immediately affect others and can be controlled. If you _know_ (guaranteed by management) that the schema will _never_ cross reference, then I'd still go for single DB, unless there is a proven need for separate database.

I know developers like to have a whole database for themselves, but unfortunately all schema co-exist in the database, so should developers in one DB.

A. Bahar, I didn't understand your point, so pardon me. What statistics are we talking here? You mean if ytou have on database per schema, table stats will be different than having all schema in one DB ??

Raj
--------------------------------------------------------------------------------
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !

DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.