It's ODBC, I think. The MS ODBC driver (are they using ODBC? If so, is it
an MS driver or an Oracle driver?) tends to do SELECTs like this in lieu of
a DESCRIBE. They don't fetch from the cursors; they just read the
select-column information returned in order to perform a crude DESCRIBE of
the
Dennis,
Ask Anjo about his Magic utility. Using that utility one has to set an environment
variable on the client which would tune and avoid extra parse sql before they are sent
to Oracle. Infact Cary mentions about this in his emails.
btw we use delphi 3rd party ODAC component instead of ADO/
Boy, I go to a new job and I don't have any of my old notebooks. I remember
something like this from the past from a third-party app. The first three
queries would just be verifying the existance of the object. Can't remember
if it was via a SELECT * (I don't think so) or some other similar query.
That's one way to get a 99.99% buffer cache hit ratio for the statement!
-Original Message-
Sent: Wednesday, September 25, 2002 11:54 AM
To: Multiple recipients of list ORACLE-L
Hello all
I am trying to debug a mysterious sporadic error that a Visual Basic
program using ADO is hittin
Dennis,
I've seen ADO do some pretty strange stuff "under the covers" on my project
also. Ny guess is that ADO is sending these sql statements kinda like a
"prepare" statement, just to see if the query will pass muster - like basic
security checks - does the table exists, etc. My guess is that
Okay, I think I answered my own question. If you look at the "Fetch" line on
the select * calls, it is zero. My guess is that ADO is just checking for
the existence of each table before it makes the real SQL call.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
