|Subject||Re: [firebird-support] Re: Stumped on SQL Indexing/Bad Plan-ing|
|Author||Ismael L. Donis Garcia|
The join you should always avoid them, if and when it is possible to use filters where instead of join and besides you should try than the ones join that you use use them with numerical fields since this comes for the way of bringing about this instruction, this not only you should apply it in firebird but in all the systems of SQL that you use.
|| ISMAEL ||
|| ISMAEL ||
----- Original Message -----
Sent: Thursday, August 11, 2011 10:47 AM
Subject: [firebird-support] Re: Stumped on SQL Indexing/Bad Plan-ing
Here is the PLAN that goes with that SQL. I should have included it in the first message.
PLAN SORT (SORT (JOIN (S INDEX (IDX_JET_SAV_PNT5), L INDEX (IDX_JET_CHG_LOG3), F INDEX (UNQ_JET_FLD_NMS_2), T INDEX (UNQ_JET_TBL_NMS_1))))
When I execute this the first time, it takes 9 seconds. I think the 6 second saving was only because I was re-executing it and FB kept a cache or something that helped out the subsequent executions.
The 2 SORTs at the begining are probably what's killing my timings. Should I add an index some where to get rid of them?
Thanks in advance for any help you can provide. This is the only remaining "slow point" in my application. (After 10 months of programming)
[Non-text portions of this message have been removed]