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) */
Dig Deeper on Oracle and SQL
-
![]()
What are the best database testing tool features for testers?
By: Amy Reichert
-
![]()
Using SQL Access Advisor to improve indexes and materialized views
By: Matthew Morris
-
![]()
SQL Server views: Creating indexes and adding base data
By: Robert Sheldon
-
![]()
SQL Server views: What they are and how to create them
By: Robert Sheldon
