MyISAM is based on the older (and no longer
ISAM storage engine but has many
Table 16.2 MyISAM Storage Engine Features
|Backup/point-in-time recovery (Implemented in the server, rather than in the storage engine.)||Yes|
|Cluster database support||No|
|Compressed data||Yes (Compressed MyISAM tables are supported only when using the compressed row format. Tables using the compressed row format with MyISAM are read only.)|
|Encrypted data||Yes (Implemented in the server via encryption functions.)|
|Foreign key support||No|
|Full-text search indexes||Yes|
|Geospatial data type support||Yes|
|Geospatial indexing support||Yes|
|Replication support (Implemented in the server, rather than in the storage engine.)||Yes|
|Update statistics for data dictionary||Yes|
MyISAM table is stored on disk in two files.
The files have names that begin with the table name and have an
extension to indicate the file type. The data file has an
MYData) extension. The
index file has an
MYIndex) extension. The table definition is
stored in the MySQL data dictionary.
To specify explicitly that you want a
table, indicate that with an
ENGINE table option:
CREATE TABLE t (i INT) ENGINE = MYISAM;
In MySQL 8.0, it is normally necessary to use
ENGINE to specify the
storage engine because
InnoDB is the default
You can check or repair
MyISAM tables with the
mysqlcheck client or myisamchk
utility. You can also compress
MyISAM tables with
myisampack to take up much less space. See
Section 4.5.3, “mysqlcheck — A Table Maintenance Program”, Section 4.6.4, “myisamchk — MyISAM Table-Maintenance Utility”, and
Section 4.6.6, “myisampack — Generate Compressed, Read-Only MyISAM Tables”.
In MySQL 8.0, the
engine provides no partitioning support. Partitioned
MyISAM tables created in previous versions of
MySQL cannot be used in MySQL 8.0. For more
Section 23.6.2, “Partitioning Limitations Relating to Storage Engines”. For help
with upgrading such tables so that they can be used in MySQL
Section 2.11.4, “Changes in MySQL 8.0”.
MyISAM tables have the following characteristics:
All data values are stored with the low byte first. This makes the data machine and operating system independent. The only requirements for binary portability are that the machine uses two's-complement signed integers and IEEE floating-point format. These requirements are widely used among mainstream machines. Binary compatibility might not be applicable to embedded systems, which sometimes have peculiar processors.
There is no significant speed penalty for storing data low byte first; the bytes in a table row normally are unaligned and it takes little more processing to read an unaligned byte in order than in reverse order. Also, the code in the server that fetches column values is not time critical compared to other code.
All numeric key values are stored with the high byte first to permit better index compression.
Large files (up to 63-bit file length) are supported on file systems and operating systems that support large files.
There is a limit of (232)2 (1.844E+19) rows in a
The maximum number of indexes per
MyISAMtable is 64.
The maximum number of columns per index is 16.
The maximum key length is 1000 bytes. This can also be changed by changing the source and recompiling. For the case of a key longer than 250 bytes, a larger key block size than the default of 1024 bytes is used.
When rows are inserted in sorted order (as when you are using an
AUTO_INCREMENTcolumn), the index tree is split so that the high node only contains one key. This improves space utilization in the index tree.
Internal handling of one
AUTO_INCREMENTcolumn per table is supported.
MyISAMautomatically updates this column for
UPDATEoperations. This makes
AUTO_INCREMENTcolumns faster (at least 10%). Values at the top of the sequence are not reused after being deleted. (When an
AUTO_INCREMENTcolumn is defined as the last column of a multiple-column index, reuse of values deleted from the top of a sequence does occur.) The
AUTO_INCREMENTvalue can be reset with
ALTER TABLEor myisamchk.
Dynamic-sized rows are much less fragmented when mixing deletes with updates and inserts. This is done by automatically combining adjacent deleted blocks and by extending blocks if the next block is deleted.
MyISAMsupports concurrent inserts: If a table has no free blocks in the middle of the data file, you can
INSERTnew rows into it at the same time that other threads are reading from the table. A free block can occur as a result of deleting rows or an update of a dynamic length row with more data than its current contents. When all free blocks are used up (filled in), future inserts become concurrent again. See Section 8.11.3, “Concurrent Inserts”.
You can put the data file and index file in different directories on different physical devices to get more speed with the
INDEX DIRECTORYtable options to
CREATE TABLE. See Section 13.1.20, “CREATE TABLE Syntax”.
NULLvalues are permitted in indexed columns. This takes 0 to 1 bytes per key.
Each character column can have a different character set. See Chapter 10, Character Sets, Collations, Unicode.
There is a flag in the
MyISAMindex file that indicates whether the table was closed correctly. If mysqld is started with the
MyISAMtables are automatically checked when opened, and are repaired if the table wasn't closed properly.
myisamchk --analyze stores statistics for portions of keys, as well as for entire keys.
MyISAM also supports the following features:
A forum dedicated to the
MyISAMstorage engine is available at https://forums.mysql.com/list.php?21.