On Mon, Aug 22, 2011 at 01:45:11PM +0200, Jonathan Hoser wrote:
Hello Tomas,
yes, of course I know that an 'ORDER BY' will actually increase the CPU
effort for the query.
However, my consideration was: Why is the original query running eternally?
My thoughts were: The IDs to be filtered
Hello Tomas,
yes, of course I know that an 'ORDER BY' will actually increase the CPU
effort for the query.
However, my consideration was: Why is the original query running eternally?
My thoughts were: The IDs to be filtered against in the DELETE [...]
WHERE id NOT IN ([subselect]) were randomly
Hello Jonathan,
Testdriving the two queries got me the following:
Original:still running since 30minutes now (top-CPU time)
modified: 3184ms
The speed improvement is very nice. However here're my comments:
- both DISTINCT and ORDER are syntactically correct for Oracle
- ORDER BY
