Like I said this is test.  In prod, they only have select access.
 
However, since in test have "any" rights, were able to get a sys object.

>>> [EMAIL PROTECTED] 4/12/02 9:13:19 AM >>>
Jeff,

We have dba privileges granted to schema owners in devl databases, test
database mimics the prod, so they just have appropriate roles. In prod, no
schema level access, everyone goes in with their own id, and no one has
those ANY privileges.

In next couple of months, we are cutting off developer access to prod. For
fixing bugs and debugging, we create a database (named DAYOLD) that is same
as production database at 5am that day. It's is all automatic, works fine
and all developers are getting adjusted to the fact that prod access is
going away.

Also we have a benefit of this dayold database, we can run and test all
weekly releases on the dayold database, the day before they are applied to
production, so we can catch all errors and get them fixed by developers
before the code release, this is imp because when we do the code release,
most of the developers are probably still in bed that early in the am.

Raj
______________________________________________________
Rajendra Jamadagni              MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
Sent: Friday, April 12, 2002 8:38 AM
To: Multiple recipients of list ORACLE-L


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

Reply via email to