"Isaac Blank" <izblank_at_yahoo.com> wrote in message
news:o05Ma.206$Z04.31531036_at_newssvr21.news.prodigy.com...
> "Daniel Morgan" <damorgan_at_exxesolutions.com> wrote in message
> news:3F00CE4C.E10A09DE_at_exxesolutions.com...
>
> > Fine. But the concept here is one of moving code from Development to
Test
> to
> > Production.
> >
> > When it is in production it belongs to the production DBAs, not the
> developers
> > or the testers.
>
> When there is a performance problem in production, DBAs can only
detect
> it. It is very seldom that they can fix it - usually when they themselves
> screwed it up by dropping an index or messing up statistics, etc. So they
> will turn to the developer on call for diagnostics and resolution.
Of course, the developers will do this in development, the changes will go
through QA and then be applied to production, by the production DBA.
Otherwise you don't have a change process.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Tue Jul 01 2003 - 05:02:42 CDT
