Re: Developer access in test database

> To answer your question:
> We define schema owner for each application and only the DBA knows
> the password. the user gets i, u, d, s grants on the objects but have NO
> grants to do DLL's. All DDL is done by the DBA.
>
> This role was implemented after tables began to disappear from the schema
> due to the use of tools that did things on their own.
>
> Sure, it is more work for the DBA but it is better the restoring DB or
> restoring
> tables from export while the entire team sits around drinking coffee.

We use a similar process in development cycles, where the scratch db and production DB are identical but have different passwords and rights. Makes it hard[er] to accidentally point DDL-code at the production database during testing.

One thing that helps in this situation is to have some automated tool for modifying the database. When someone wants a change they can either pass on an updated config file or some standard notation for the alteration to the DBA's. Otherwise you just get a barrage if semi-cohereint emails asking for minor changes.

enjoi.

--
Steven Lembark                               2930 W. Palmer
Workhorse Computing                       Chicago, IL 60647
                                            +1 800 762 1582
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Steven Lembark
  INET: lembark_at_wrkhors.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).