RE: Developer access in test database

[Mercadante, Thomas F]

Jeff,   Developers should only have access to stuff they need.  This does not include SYS stuff.  Basically, do you want to be restoring the development database just because somebody was playing with something?  Further, who will be blamed for the developers not being able to do their job while you are restoring the db - the developer who screwed it up, or you?   I'm all for giving developers tons of privs in the dev database - up to a point.  You need to protect yourself from them ruining your day.   To answer your question, I grant s,i,u,d to the schema tables directly to the user to that they can create stored procs if need be.  I then migrate stored procs to the dev schema as need be.   Hope this helps Tom Mercadante Oracle Certified Professional -----Original Message----- From: Jeffrey Beckstrom [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 8:38 AM To: Multiple recipients of list ORACLE-L Subject: Developer access in test database In our test databases, I have always granted select,insert,update,delete any table to the developers.   While yesterday, one updated a "sys" table.   Be non-production, I always felt if it is destroyed can always be recreated.   What table privileges do you grant in "test".   Jeffrey Beckstrom Database Administrator Greater Cleveland Regional Transit Authority 1240 W. 6th Street Cleveland, Ohio 44113 (216) 781-4204