Training, Open Source computer languages

PerlPythonMySQLTclRubyC & C++LuaJavaTomcatPHPhttpdLinux

Search our site for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
MySQL - Optimising Selects
If you're going to be doing a complex select in MySQL, how should you formulate it to make it run efficiently?

This sounds like a simple question, but is actually very complex!

Firstly, consider creating indexes on any columns that are likely to be used in the selection of joining of records; choose a UNIQUE INDEX if a field is known to be unique, and a FULLTEXT INDEX if you want to be able to quickly search a text field for a particular value. Use just an INDEX for non-unique fields. Here are some example commands that create indeexes:

create unique index piidindex on b_ptab (piid(5));
create index piidindex on b_btab (piid(5));
create fulltext index synindex on b_btab (synopsis);

Your data structure is now optimised to allow for selects searching on the indexed fields.

Secondly, when you specify your tables to be joined, try to specify the tables at the "heart" of the join operation first before the tables that tag data onto the structure; you may want to specify a STRAIGHT JOIN to force these tables to be read first.

Third, if you're selecting based on text word content
- use MATCH in preference to LIKE
- and use LIKE in preference to RLIKE

Using these techniques, a well written query can run thousands of times faster that a poor one. I'm writing this note on a laptop running MySQL and I ran a following query to join:
* A table of books
* A table of Authors
* A pivot table to link authors to books
* A table of book subject
* and a table of book publishers

Out of some 550 books (with a total of around 700 different authors), I selected the 53 records that included the word "focus" in their Synopsis, using the command:
select sql_no_cache title,fullname,b_btab.biid,b_atab.aiid,pvid,subject,pubname from b_btab, b_atab, b_pivot, b_stab, b_ptab where b_btab.biid = b_pivot.biid and b_atab.aiid = b_pivot.aiid and b_stab.biid = b_btab.biid and b_ptab.piid = b_btab.piid and match (synopsis) against ('focus');
and it took 0.02 seconds. The same join, without indexes and any optimisation, took 3 minutes and 18 seconds.

(written 2004-12-21 05:51:52)

 
Associated topics are indexed under
S157 - More MySQL Commands

Back to
MySQL - LEFT JOIN and RIGHT JOIN, INNER JOIN and OUTER JOIN
Previous and next
or
Horse's mouth home
Forward to
Review of the Autumn

Some other Articles
Introduction fees, bonuses, commissions, kickbacks
A Change is as good as a rest
Christmas break
Review of the Autumn
MySQL - Optimising Selects
MySQL - LEFT JOIN and RIGHT JOIN, INNER JOIN and OUTER JOIN
Automatic service upgrades
Signage
Railway train service, Melksham station
Linux - where to put swap space
1771 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36 at 50 posts per page


This is a page archived from The Horse's Mouth at http://www.wellho.net/horse/ - the diary and writings of Graham Ellis. Every attempt was made to provide current information at the time the page was written, but things do move forward in our business - new software releases, price changes, new techniques. Please check back via our main site for current courses, prices, versions, etc - any mention of a price in "The Horse's Mouth" cannot be taken as an offer to supply at that price.

Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).

© WELL HOUSE CONSULTANTS LTD., 2008: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 0800 043 8225 or 01225 708225 • FAX: 0845 8382 405 or 01225 707126 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho