Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Justifying A Copy Of Production Environment

Re: Justifying A Copy Of Production Environment

From: Niall Litchfield <niall.litchfield_at_dial.pipex.com>
Date: Thu, 1 Jan 2004 16:43:45 -0000
Message-ID: <3ff44e41$0$18030$cc9e4d1f@news.dial.pipex.com>


or explain that a test system is unnecessary, but that NO os, code, report or database changes will be made to production once the system has been accepted. Management to accept the risk of lost business, security breaches, software failure... If you are happy with what you have and will never change it then that's fine. (apart from the pseudo random performance that Connor alludes to obviously).

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
"Connor McDonald" <connor_mcdonald_at_yahoo.com> wrote in message
news:3FF3886D.4DB8_at_yahoo.com...

> Robert Perry wrote:
> >
> > I am in the process of writing a document that will justify having a
> > test environment(not QA) that mirror's production. Just like many
> > companies today, our management severely scrutinizes IT budget and
> > expect miracles to be performed when a crises occur. In response to
> > this behavior, I am putting together a document that outlines the
> > pros/cons of having a test environment that mirrors production in
> > order to troubleshoot problems when they occur, test production
> > upgrades, etc.
> >
> > I am using my 10 years + of Oracle experience as a DBA and the Oracle
> > 24X7 book as my primary sources. Can anyone point me to additional
> > books or documents to consider? Documentation that includes REAL
> > WORLD examples of how executive management shot themselves in the foot
> > by not mirroring their production environment would be a PLUS.
> >
> > Thanks
>
> Just put in the document that a full size test database is not required,
> but also a little disclaimer asking them to sign that they understand
> and will take responsbility for the fact performance, scalability, and
> data integrity are now pseudo-random as opposed to predictable and
> controllable.
>
> Cheers
> Connor
Received on Thu Jan 01 2004 - 10:43:45 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US