I grant them full access to their own
schema. The production schema owner in TEST databases is still controlled
by DBAs. I do grant them selected '... any ...' privileges as needed, in
the TEST databases excluding 'select any table'. No one gets it. Instead I
grant them select_catalog_role to view SYS owned views etc. In addition, I have
created a TOAD_USER role for them to use TOAD fully without running into any
problems. These things have cut down a lot of very basic questions and calls
from Developers. However, one size does not fit all. This is all dependent on how developement work
is done in your particular environment. In my previous job, no one bothered to
change sys and system passwords and it was a true 'open systems' environment
when it came to TEST/DEV work !!
- Kirti
-----Original
Message-----
From: Kimberly Smith [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 8:58 AM To: Multiple recipients of list ORACLE-L Subject: RE: Developer access in test database
|
- Developer access in test database Jeffrey Beckstrom
- RE: Developer access in test database Jamadagni, Rajendra
- RE: Developer access in test database Mercadante, Thomas F
- RE: Developer access in test database Jeffrey Beckstrom
- RE: Developer access in test database Mercadante, Thomas F
- RE: Developer access in test database Kimberly Smith
- Re:RE: Developer access in test database dgoulet
- RE: RE: Developer access in test database Deshpande, Kirti
- RE: RE: Developer access in test database Mercadante, Thomas F
- RE: Developer access in test database John Hallas
- Re: Developer access in test database Suzy Vordos
- Re: Developer access in test database Suzy Vordos
- RE: Developer access in test database DENNIS WILLIAMS
- RE: Developer access in test database Whittle Jerome Contr NCI
- Re: Developer access in test database Yechiel Adar
- Re: Developer access in test database Steven Lembark