Re: 39 MILLION ROW MARCH (USING MyISAM)
Posted by:
James Day
Date: November 22, 2005 10:22PM
Interesting approach, but why not just use the InnoDB storage engine with the primary key/physical order set appropriately, then use "covering indexes" for time-critical queries? You can use covering indexes with MyISAM as well. A covering index is an index which contains every field used in the select.
Your data set seems fairly small, so you're unlikely to have great problems doing it that way.
If most queries are for only a few fields there is often benefit in moving the other fields into a table of their own, leaving just the commonly queried fields in the main table.
James Day
Support engineer, MySQL AB
Subject
Views
Written By
Posted
2463
November 03, 2005 07:05AM
1246
November 03, 2005 04:36PM
1348
November 16, 2005 05:26PM
1357
November 16, 2005 06:42PM
1352
November 16, 2005 06:51PM
1394
November 17, 2005 05:24PM
1284
November 16, 2005 07:35PM
1477
November 17, 2005 05:19PM
1232
November 17, 2005 06:38PM
1358
November 18, 2005 07:56PM
1312
November 29, 2005 12:48PM
1257
November 29, 2005 12:50PM
Re: 39 MILLION ROW MARCH (USING MyISAM)
1380
November 22, 2005 10:22PM
Sorry, you can't reply to this topic. It has been closed.
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.