Re: SQL Newbie needs urgently help! [optimizing query]
Hm, I wonder about MySQL's decision for the index usage. Categories, aka item_t1, is joined last and there's a condition that can use the primary key of that table.
Could you try adding "FORCE INDEX(PRIMARY)" right after "Categories item_t1"? Maybe MySQL tries to avoid reading the value for SourcePK (key_len 92 seems huge), but there are only two rows expected to be read, which should make that still perform a lot better than reading 18000 rows from Categories to perform the checks for the other conditions...
Subject
Views
Written By
Posted
3560
January 24, 2007 05:31AM
2354
January 24, 2007 05:52AM
2259
January 24, 2007 06:07AM
2307
January 24, 2007 06:18AM
2171
January 24, 2007 06:41AM
2187
January 24, 2007 07:16AM
2267
January 24, 2007 08:16AM
2348
January 24, 2007 08:50AM
2190
January 24, 2007 09:10AM
2306
January 24, 2007 09:24AM
2431
January 24, 2007 10:29AM
2256
January 24, 2007 10:40AM
Re: SQL Newbie needs urgently help! [optimizing query]
2193
January 24, 2007 03:19PM
2115
January 25, 2007 07:27AM
2168
January 24, 2007 07:16AM
2341
January 24, 2007 07:32AM
Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
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.