Re: V$ tables

He's being a plonker.

With attitude like that, he deserves to be working with Access "databases".

Regards
HJR "Charlie Edwards" <Charlie3101_at_hotmail.com> wrote in message news:db479d88.0206180052.5546ec_at_posting.google.com...
> Well I asked my DBA for SELECT_CATALOG_ROLE and this is the
> (paraphrased) reply I got ...
>
> "There is certainly a security issue with SELECT_CATALOG_ROLE so
> access to this will not be granted.
>
> I have granted access to all those v$ views that I considered useful
> for application tuning and did not compromise database security.
>
> If access is to be granted to any other v$ views then their usefulness
> to application tuning will need demonstrating to me and I will need to
> satisfy myself they pose no security risks"
>
> I feel like shooting myself (or preferably him)
> :-(((((
>
> CE
>
> Daniel Morgan <dmorgan_at_exesolutions.com> wrote in message
news:<3D0A137B.F00D3EC9_at_exesolutions.com>...
> >
> > Please allow me to ask the question in a different way. What possible
> > justification is there for not giving developers access to all v_$
> > views? And for that matter all dba_ views too?
> >
> > Can they change anything?
> > Can they do any damage?
> > Is there a negative side to having developers that know and care about
> > how their work will impact production?
> >
> > Give them the whole darned thing and be glad they asked.
> >
> > The only reason I have ever felt for DBAs denying access to the data
> > dictionary views (other than ego) is that they are so insecure with
> > their own skills that they are afraid someone might see that they
> > haven't been doing their job well.
> >
> > Daniel Morgan
Received on Tue Jun 18 2002 - 04:04:33 CDT