Jared Still wrote:
> On Tue, 07 Dec 2004 22:07:31 -0800, DA Morgan wrote:
>
>
>>n_kselva_at_yahoo.com wrote:
>>
>>
>>>Hello,
>>>
>>>I am a startup DBA.I read in a tuning book that one should grant
>>>privileges on v$ views to non DBA users as needed and use caution.
>>>and it involves performance costs.I do not know which situation could
>>>demand a non DBA to access the v$ view.Also what are the other
>>>problems/concern associated with this grant of privilege. I do not find
>>>deeper discussion in books.I apologize if i have not correctly used
>>>this forum.
>>>
>>>Thanks in advance for the help.
>>>
>>>Regards,
>>>Selva.
>>
>>Depends on whether you are talking about development, testing, or a
>>production database. I can easily see a production application requiring
>>access to v$mystat, v$session, and others depending on functionality.
>>
>>In a development database I can't think of a single reason why everyone
>>should not have access to v$reserved_words.
>
>
> How about developers thrashing the development database with
> frequent selects on v$sqlarea, or other expensive to use v$ views?
>
> I don't think anyone other than the DBA needs unfettered
> access to all the v$ views.
>
> And not even all of them can be trusted.
I stated every developer should have access to v$reserved_words. You
responded with "all the v$ views". There is more then a slight
disconnect between the two.
--
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)
Received on Thu Dec 09 2004 - 10:07:18 CST
