Re: Best way to manage developers/schemas

LOL,
No is the answer, ask Why? I am pretty sure you will not get a suitable answer. Then your answer should be a resounding NO.

Ideally, you should manage schema objects as schema owner. This is probably a request to gain _any_ type privs. Did I mention your answer should be NO, even in development?

Raj

On 5/25/05, Paula_Stankus_at_doh.state.fl.us <Paula_Stankus_at_doh.state.fl.us> wrote:
>
> My developer wants to have the ability from one login to manage objects
> in another login (i.e. create table, index, drop table, index).
> However, there is only a create any ... Drop any... That would be global
> and that would be really a bad idea. Can I give them access to
> create/drop just in a specific schema from another schema?
>

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