Re: Help on Query with DATE BETWEEN not performant

[Kristijan Marin]

Hi,

Yes I did try forcing it ... but what it is doing is it fetches articles from earticles table first and then filter it by the date... and that was 1.3mil rows,

instead of filtering only the 41k articles got from earticle_contract table and do the filtering only on that set ...

I did create a new index as you suggested already, with date & id, but the result was the same ...


The thing is that the database is working the same as before where we had no buffer pool size and only 1 instance by default ...

I will try with fewer instances ... and disable cache ...

Is there anything I should look for in my database like using more disk then memory, i/o operations, hard parses, etc ...

that would explain why joins are so slow in this situation or why explain plan is showing wrong estimations?

Thanks,
Kris