RE: two databases in a server

From: Kevin Closson <kevinc_at_polyserve.com>
Date: Fri, 31 Mar 2006 14:08:57 -0800
Message-ID: <5D2570CAFC98974F9B6A759D1C74BAD06FE618@ex2.ms.polyserve.com>

I suspect you don't have very many databases (over 50) in production?

---

        From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Thomas Day

	Sent: Friday, March 31, 2006 9:46 AM
	To: oracle-l_at_freelists.org
	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.

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Mar 31 2006 - 16:08:57 CST