ARCHIVE storage engine produces
special-purpose tables that store large amounts of unindexed data in
a very small footprint.
Table 15.5 ARCHIVE Storage Engine Features
|Backup/point-in-time recovery (Implemented in the server, rather than in the storage engine.)||Yes|
|Cluster database support||No|
|Encrypted data||Yes (Implemented in the server via encryption functions.)|
|Foreign key support||No|
|Full-text search indexes||No|
|Geospatial data type support||Yes|
|Geospatial indexing support||No|
|Replication support (Implemented in the server, rather than in the storage engine.)||Yes|
|Update statistics for data dictionary||Yes|
ARCHIVE storage engine is included in MySQL
binary distributions. To enable this storage engine if you build
MySQL from source, invoke CMake with the
To examine the source for the
look in the
storage/archive directory of a
MySQL source distribution.
You can check whether the
ARCHIVE storage engine
is available with the
When you create an
ARCHIVE table, the server
creates a table format file in the database directory. The file
begins with the table name and has an
extension. The storage engine creates other files, all having names
beginning with the table name. The data file has an extension of
.ARN file may
appear during optimization operations.
ARCHIVE engine supports
SELECT, but not
UPDATE. It does support
ORDER BY operations,
BLOB columns, and basically all data
types including spatial data types (see
Section 11.4.1, “Spatial Data Types”). Geographic spatial
reference systems are not supported. The
engine uses row-level locking.
ARCHIVE engine supports the
AUTO_INCREMENT column attribute. The
AUTO_INCREMENT column can have either a unique or
nonunique index. Attempting to create an index on any other column
results in an error. The
ARCHIVE engine also
AUTO_INCREMENT table option in
CREATE TABLE statements to specify
the initial sequence value for a new table or reset the sequence
value for an existing table, respectively.
ARCHIVE does not support inserting a value into
AUTO_INCREMENT column less than the current
maximum column value. Attempts to do so result in an
ARCHIVE engine ignores
BLOB columns if they are not
requested and scans past them while reading.
Storage: Rows are compressed as
they are inserted. The
ARCHIVE engine uses
zlib lossless data compression (see
http://www.zlib.net/). You can use
OPTIMIZE TABLE to analyze the table
and pack it into a smaller format (for a reason to use
OPTIMIZE TABLE, see later in this
section). The engine also supports
TABLE. There are several types of insertions that are
INSERTstatement just pushes rows into a compression buffer, and that buffer flushes as necessary. The insertion into the buffer is protected by a lock. A
SELECTforces a flush to occur, unless the only insertions that have come in were
INSERT DELAYED(those flush as necessary). See Section 22.214.171.124, “INSERT DELAYED Statement”.
A bulk insert is visible only after it completes, unless other inserts occur at the same time, in which case it can be seen partially. A
SELECTnever causes a flush of a bulk insert unless a normal insert occurs while it is loading.
Retrieval: On retrieval, rows are
uncompressed on demand; there is no row cache. A
SELECT operation performs a complete
table scan: When a
SELECT occurs, it
finds out how many rows are currently available and reads that
number of rows.
SELECT is performed
as a consistent read. Note that lots of
SELECT statements during insertion
can deteriorate the compression, unless only bulk or delayed inserts
are used. To achieve better compression, you can use
OPTIMIZE TABLE or
REPAIR TABLE. The number of rows in
ARCHIVE tables reported by
SHOW TABLE STATUS is always accurate.
See Section 126.96.36.199, “OPTIMIZE TABLE Statement”,
Section 188.8.131.52, “REPAIR TABLE Statement”, and
Section 184.108.40.206, “SHOW TABLE STATUS Statement”.
A forum dedicated to the
ARCHIVEstorage engine is available at https://forums.mysql.com/list.php?112.