Re: Query not always using indexes
In the slow run, ref=ALL means the optimiser could not find an `sch` index that would be faster than a table scan. To have a chance at suggesting an improvement, we'd need to see the two update queries and Show Create Table results for the referenced tables.
Subject
Views
Written By
Posted
2800
January 06, 2017 05:48AM
Re: Query not always using indexes
935
January 06, 2017 12:28PM
1045
January 09, 2017 05:18AM
909
January 09, 2017 02:30AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.