Re: Access to V$ views

"Jaap W. van Dijk" wrote:

> I can imagine, with your background, you must feel blind without
> access to the v$ views. But do you *really* need them as a developer?
>
> My strategy is: in the development environment the developers are
> welcome to muck up the database as much as they like, but as soon as
> things pass to system and acceptance test environment the database is
> my ballpark, and the only one that makes changes to it is me or my dba
> colleagues, because I am responsible for the reliability of the test
> results as far as the schema is concerned.
>
> Jaap.
>
> On 7 May 2002 05:17:38 -0700, esicl_at_aol.com (Ed) wrote:
>
> >Hi,
> >
> >My DBA is very protective about everything. For example, recently he
> >threatened to take CREATE TABLE privilege away from me as I had
> >committed the heinous crime (on a development machine) of creating a
> >table without the storage clause! By the way, I have over 10 years
> >experience developing in Oracle (I remember V5), and I used to be a
> >DBA.
> >
> >How can I him to give me access to the V$ views? i.e. What are the
> >possible reasons for and against granting access to these views to
> >developers?
> >
> >I would be grateful for a few suggestions, as this my prevent me
> >killing him, and I wouldn't want to deprive my children of their
> >father.
> >
> >Thanks,
> >
> >Ed

Need them? They are absolutely essential if you are to do a half-way decent job. How can you develop good code without access to information about the impact of what you are writing on the instance?

Without looking at the V_$ objects basically all the developer is doing is passing along performance and scalability problems to the production DBA who likely has plenty on his or her plate already.

Daniel Morgan Received on Tue May 07 2002 - 15:12:56 CDT