Re: Slow update with two like 'string%' conditions
Hi Oleg,
This query could be much more performant if you could rely on exact matching of symbol and/or name instead of partial matching. The way it is now, all records
in final table with fdate between q.namedt and q.nameendd will have to be checked for every row of crsp_stocknames table. If exact matching could be done, a multi-column index on (symbol, name, datef) would be able to limit the number of rows to
be inspected significantly.
The way it is now, I do not on top of my head see any way to get this query to perform better.
Øystein Grøvlen,
Senior Principal Software Engineer,
MySQL Group, Oracle,
Trondheim, Norway
Subject
Views
Written By
Posted
2091
March 25, 2014 04:09PM
Re: Slow update with two like 'string%' conditions
847
March 26, 2014 03:41AM
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.