Skip to Main Content

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Use of DRIVING_SITE hint for query on remote database

734426Jun 17 2010 — edited Jun 18 2010
hi -- I've run across a performance problem doing some queries on remote databases in Application Express. My suspicion (after posting to the APEX forum and doing extensive testing) is that APEX is the main source of the problem... as I have no performance issues doing the same queries in SQL*Plus.

However, one suggestion was to use the DRIVING_SITE hint to help optimize the query. I understand the concept, but from what I've read about it, it probably won't do much good in my case:

While I might be joining 3 or 4 or 5 tables together, ALL of the tables are on the remote database. Will Oracle -- always -- already be executing the entire query on the remote db?

In the future I may have situations where the query accesses tables on more than one database: in that case, do I gather correctly that the DRIVING_SITE able should be the one with the most data? (Probably an oversimplification, but...)

Thanks!
Carol
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 16 2010
Added on Jun 17 2010
2 comments
989 views