Well, if oracle stores all the meta data in UPPERCASE, then for a query in
which object names are written in lowercase characters will force the parser
to convert it into UPPERCASE for comparison, in which case there should be a
negligible difference if the name of the objects referenced by the qu
I never said both wouldn't be listed separately... in fact I said they
WOULD.
I said cursor_sharing would NOT change case, but would only affect the
statement if you used a literal in it.
--- "Mercadante, Thomas F" <[EMAIL PROTECTED]> wrote:
> Rachel,
>
> This is what I thought, but list member
Rachel,
This is what I thought, but list members say differently.
I just tried a simple test:
Ran the following two queries:
select count(*) from tomsqltest;
SELECT COUNT(*) FROM TOMSQLTEST;
and then:
select hash_value,executions,sql_text from v$sql
where upper(sql_text) like '%TOMSQLTEST%'
Title: RE: Does the case of an Oracle query statement affect query perform
Thanks Tim, I didn't knew these differences between PROC/PLSQL and other modules ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadag
> I don't have papers to substantiate this, but in our 9012 database
> before we
> started using cursor_sharing we used to run out of our 600M SGA, but
> since
> we started using CS, it went down.
That should have nothing to do with the case of a statement and
everything to do with using literal
essage -
From:
Mercadante, Thomas F
To: Multiple recipients of list ORACLE-L
Sent: Monday, September 30, 2002 7:48
AM
Subject: RE: Does the case of an Oracle
query statement affect query perfo
Raj,
Do
you have any test cases or white papers to support your st
I believe Raj is referring to the fact that Oracle will reuse SQL
from the SQL Cache if the statement has been parsed already, but they
must match verbatim.
for example:
a)SELECT column1, column2 FROM table WHERE column0 = 5;
b)SELECT COLUMN1, COLUMN2 FROM TABLE WHERE COLUMN0 =5;
will b
Title: RE: Does the case of an Oracle query statement affect query perfo
Tom,
Well it simply comes to when Oracle will parse the query and try to find a "matching" sql to hash to in SGA, if it finds one, it will hash to the same one, else it will have to create a new hash entry.
--Original Message-From: Jamadagni, Rajendra
[mailto:[EMAIL PROTECTED]]Sent: Monday, September 30,
2002 8:33 AMTo: Multiple recipients of list
ORACLE-LSubject: RE: Does the case of an Oracle query statement
affect query perfo
As long as you stick to either (a) or (b) you will be o
Datta
[mailto:[EMAIL PROTECTED]]Sent: Monday, September 30, 2002
2:58 AMTo: Multiple recipients of list ORACLE-LSubject:
Does the case of an Oracle query statement affect query
performance?
Hi,
Pardon me for such a naive question, coz I am a novice when it comes to Oracle.
This is basically
No, there will not be any noticable difference in performance.
-Mark
On Mon, 2002-09-30 at 03:58, Shantanu Datta wrote:
> Hi,
> Pardon me for such a naive question, coz I am a novice when it comes to
> Oracle. This is basically got to do with how Oracle parses a query.
>
> Consider the f
s the case of an Oracle query statement affect query
performance?
Hi,
Pardon me for such a naive question, coz I am a novice when it comes to
Oracle. This is basically got to do with how Oracle parses a
query.
Consider the following queries:
a) SELECT co
Hi,
Pardon me for such a naive question, coz I am a novice when it comes to Oracle.
This is basically got to do with how Oracle parses a query.
Consider the following queries:
a)
SELECT column1, column2 FROM table WHERE column0 = 5;
b)
SELECT COLUMN1, COLUMN2 FROM TABLE
13 matches
Mail list logo
