quot; <[EMAIL PROTECTED]>
> Organization: Fat City Network Services, San Diego, California
> Reply-To: [EMAIL PROTECTED]
> Date: Mon, 11 Jun 2001 06:25:50 -0800
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> Subject: RE: sys.v_$parameter
>
> To by
To bypass the view? Is it in a huge script? Could be to glean every bit of
performance from the script..
Mark
-Original Message-
Sent: Monday, June 11, 2001 09:25
To: Multiple recipients of list ORACLE-L
Why would someone write a SQL*Plus script against sys.v_$parameter when you
want t
There is only one case when you should use V_$something instead of V$SOMETHING, which
is when connected as SYS (or INTERNAL) to grant SELECT to a user who needs to create a
stored procedure or view involving the said V$something.
As Vladimir said, V$xxx is a synonym for V_$xxx, which is a (hard-
What's more interesting is of course a query against v$fixed_view_definition to
show how v$parameter (or v_$parameter) is defined. This will point you to
x$ksppi and other x$-tables where you can also see the un-documented parameters
(those starting with an _).
Greg Moore wrote:
> Why would some
If you're obsessive about performance - its avoiding
the synonym lookup I suppose..
Cheers
Connor
--- Greg Moore <[EMAIL PROTECTED]> wrote: > Why
would someone write a SQL*Plus script against
> sys.v_$parameter when you
> want to find the value of an init parm, when instead
> you could code agai
On Jun 11, 2001 at 12:25:22AM, Greg Moore wrote:
> Why would someone write a SQL*Plus script against sys.v_$parameter when you
> want to find the value of an init parm, when instead you could code against
> v$parameter?
In fact you'll get the same result.
v$parameter is a synonym for v_$parameter
