Daniel, List
Can you give more detail with an EXAMPLE please ?
Thanks
-Original Message-
Sent: Friday, June 06, 2003 7:05 PM
To: Multiple recipients of list ORACLE-L
I have used an inline view to reduce network traffic when retrieiving
data from a remote db. Instead of using a nested
it) gives even better performance. Why?
Well you are saying on the database side:
Get everything from this query and put it in the REF Cursor, then in one pass send the
whole REF Cursor to the client.
Also you need inline views to solve some questions. Such as how to get records M
through N from
In one case, the statement's execution plan used a nested loop, where it read the
local table then probed the index on the remote table. This caused several million
trips across the network to retrieve less than 10,000 records (IIRC).
select local.cola, local.colb, remote.colc, remote.cold
from
Where are they advantageous to use where not ?
Thanks
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: VIVEK_SHARMA
INET: [EMAIL PROTECTED]
Fat City Network Services-- 858-538-5051 http://www.fatcity.com
San Diego, California-- Mailing list and web
What I remember from an old post regarding this issue, You don't have to
create another object, view, to workaround your requirement.
Ramon E. Estevez
[EMAIL PROTECTED]
809-535-8994
-Original Message-
VIVEK_SHARMA
Sent: Friday, June 06, 2003 8:10 AM
To: Multiple recipients of list
I have used an inline view to reduce network traffic when retrieiving
data from a remote db. Instead of using a nested loop and making
multiple trips, it made 1 trip and brought over all of the data. The
query time was reduced from 30 minutes to 5 minutes.
--
Daniel W. Fink
Title: RE: inline views
it is also useful when you DBA won't allow you to create a new view ...
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD
Here is one case where an inline view is adventageous. PL/SQL may work
better, but the requirement is a single SQL statement.
Display a single employee from each department. The employee displayed
should be a random selection and not just the first one retrieved from
the table.
(extra columns
