| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Development projects: Multiple databases v/s multiple schemas
Thanx
Raj and Bahar,
<FONT face=Arial color=#0000ff
size=2>
Raj I
think you misunderstood my question. Or I might be misunderstanding a part of
your reply :-)
<FONT face=Arial color=#0000ff
size=2>
I'll
try to make my question clearer....
<FONT face=Arial color=#0000ff
size=2>
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.
<FONT face=Arial color=#0000ff
size=2>
We are
planning to centralize the same and <SPAN
class=533142913-20062003>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?
<FONT face=Arial color=#0000ff
size=2>
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.
<FONT face=Arial color=#0000ff
size=2>
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.
<FONT face=Arial color=#0000ff
size=2>
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.
<FONT face=Arial color=#0000ff
size=2>
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).
<FONT face=Arial color=#0000ff
size=2>
<SPAN
class=533142913-20062003>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.
<SPAN
class=533142913-20062003>
<FONT face=Arial color=#0000ff
size=2>Regards
<FONT face=Arial color=#0000ff
size=2>Naveen
<FONT face=Arial color=#0000ff
size=2>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<FONT face=Tahoma
size=2>-----Original Message-----From: Jamadagni, Rajendra
[mailto:[EMAIL PROTECTED]Sent: Friday, June 20, 2003
7:35 PMTo: Multiple recipients of list ORACLE-LSubject:
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.
 |
 |