https://dev.mysql.com/converting-tables-to-innodb.html
When you convert MyISAM tables that are large, frequently accessed, and hold vital data, investigate and consider the innodb_file_per_table and innodb_page_size configuration options, and the ROW_FORMAT and KEY_BLOCK_SIZE clauses of the CREATE TABLE ... If you have MyISAM tables that you want to convert to InnoDB for better reliability and scalability, review the following guidelines and tips before ...
https://dev.mysql.com/innodb-table-compression.html
Table compression is enabled using the ROW_FORMAT=COMPRESSED attribute with CREATE TABLE or ALTER TABLE. This section describes InnoDB table compression, which is supported with InnoDB tables that reside in file_per_table tablespaces or general ...
https://dev.mysql.com/create-table-statement-retention.html
For InnoDB tables, SHOW CREATE TABLE and the Create_options column reported by SHOW TABLE STATUS show the actual ROW_FORMAT and KEY_BLOCK_SIZE attributes used by the table. The original CREATE TABLE statement, including all specifications and table ...
https://dev.mysql.com/mysql-cluster-option-tables.html
The following table provides a list of the command-line options, server and status variables applicable within mysqld when it is running as an SQL node in an NDB Cluster. For a table showing all command-line options, server and status variables ...
https://dev.mysql.com/create-temporary-table.html
When innodb_strict_mode is enabled (the default), CREATE TEMPORARY TABLE returns an error if ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE is specified. You can use the TEMPORARY keyword when creating a table. A TEMPORARY table is visible only within the ...
https://dev.mysql.com/keywords.html
Certain keywords, such as SELECT, DELETE, or BIGINT, are reserved and require special treatment for use as identifiers such as table and column names. This may also be true for the names of built-in functions. Reserved words are permitted as ...
https://dev.mysql.com/mysql-cluster-replication-schema.html
If this becomes an issue, you may be able to conserve space by using an InnoDB tablespace for this table, changing its ROW_FORMAT to COMPRESSED, or both. Replication in NDB Cluster makes use of a number of dedicated tables in the mysql database on ...
https://dev.mysql.com/dynamic-format.html
Dynamic storage format is used if a MyISAM table contains any variable-length columns (VARCHAR, VARBINARY, BLOB, or TEXT), or if the table was created with the ROW_FORMAT=DYNAMIC table option. Dynamic format is a little more complex than static ...
https://dev.mysql.com/innodb-compression-background.html
An InnoDB table created with ROW_FORMAT=COMPRESSED can use a smaller page size on disk than the configured innodb_page_size value. Because processors and cache memories have increased in speed more than disk storage devices, many workloads are ...
https://dev.mysql.com/innodb-compression-tuning.html
\! ls -l data/test/big_table.ibd CREATE TABLE key_block_size_4 LIKE big_table; ALTER TABLE key_block_size_4 key_block_size=4 row_format=compressed; INSERT INTO key_block_size_4 SELECT * FROM big_table; commit; -- Check how much space is needed for a ... Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed ...
