Q

Hint in view code to force use of index

I have a view that joins many related tables. The view is quite slow when run wide open. Can I put a hint in the view code to force the use of an index?

I have a view that I've built for the Projects Accounting module that joins many related tables to get the Project Cost transaction detail. The view is quite slow when run wide open. One of the tables, PA_COST_DISTRIBUTION_LINES_ALL, is set to a full table scan. Is there a way I can put a hint in the view code to force the use of an index?
Yes, you can put an index hint in your SQL. For example, let's say that you want to use index Idx_Emp_id to access your Employee table. Here is the hint that could accomplish this.
 /*+ Index(Employee Idx_Emp_id) */ 
This was first published in May 2007

Dig deeper on Oracle and SQL

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide

SearchDataCenter

SearchContentManagement

SearchFinancialApplications

Close