RE: two databases in a server
- From: "Kevin Closson" <kevinc@xxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 31 Mar 2006 14:08:57 -0800
I suspect you don't have very many databases (over 50) in production?
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Thomas Day
Sent: Friday, March 31, 2006 9:46 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: two databases in a server
The way that I've always seen it is:
PRODUCTION - One server, one database. Right size the server to
the database. Easy to implement one set of policies and procedures that
meet the production requirements. Server/database downtime is easier to
schedule.
DEVELOPMENT/TEST/TRAINING - Stick them all on one box in
different databases. Much more flexibility in policies and procedures.
For downtime - just tell them it'll be down. They'll complain but the
business won't suffer. Make sure that your have an SGA/Disk Csar who is
responsible for allocating computer resources.
I've never had any real problems with that.
Other related posts:
