Re: developers privileges in TEST

We have a 4 tier model where possible.

DEV - where the developers work
QAS - quality assurance - users will test changes here
PRD - obvious.

A very few folks will get SELECT access on tables. Never do they get DML access.

The 4th tier? That is TST

TST is where we can destroy things. Patches are first tested on TST systems. New procedures are tested their.

There could conceivably be a 5th tier, the DBA tier.

This is where DBA's and Developers can have free reign to try anything without worrying about adversely impacting anyone's work.

The difference between TST and DBA is that TST is a clone of a production system, while DBA can be just about anything.

DBA is where you practice with BBED. ;)

Jared

On 2/1/07, Dennis Williams <oracledba.williams_at_gmail.com> wrote:
>
> Jeff,
>
> I think it depends on your site's operational model.
> - Some sites implement a three-tier model,
> - dev, developer's playground
> - test, recent clone of production. No developer access.
> Production change scripts are executed here to verify they are ready to run
> on production
> - prod, only approved changes are made.
>
> In this model, developers only have access on development.
>
> Sometimes the game is different for a new data warehouse project that has
> few developers.
>
> Dennis Williams
>

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

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