Naveen
Advantages of single instance
- Easier to administer. I have multiple test instances and often have to
go around getting permission to bounce instances to re-jigger the memory
when one project needs more memory for some test.
- Easier to share data among projects.
Advantages of multip
Title: RE: Development projects: Multiple databases v/s multiple schemas
That's why my question ... do schema cross-reference ...?
If you have schema that don't need to talk to each other, one DB is still
good. If you have enough resources, then give every team on db. But that
Title: RE: Development projects: Multiple databases v/s multiple schemas
I understand now, but in development?? I have 13 schema that form an
application, the development is an exact replica of production RAC instance and
no one in Devl complains (well most of the times).
Raj
Title: RE: Development projects: Multiple databases v/s multiple schemas
Hi Rajendra
...
For
Example ,
There is one instance and two project on this
instance.
ProjectA and ProjectB.
beetween 10:00 am and 11:30 am , ProjectA realized via
numerious sessions
30 times wait
Naveen,
It depends on the deployment method to be used. In general I try to limit the
number of instances. Sure not having each project in it's own instance diminishes
some of the capabilities that you have to monitor how they perform, but all of those
instances are competing on the s
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
Hi,
We end up doing it both ways at the same time. We have multiple
development instances and multiple schemas in each instance. We do this
because we are running a large ERP system and each test instance has
specific testing requirements so we end up replicating multiple instances
on the same m
Title: 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
if you create separete databases , you can monitor statistics of each of them
indivudually. Otherwiese database statistics will be affected from multiple projects .
-Original Message-
Sent: Friday, June 20, 2003 2:19 PM
To: Multiple recipients of list ORACLE-L
Hi,
For multiple projec
