ANALYZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE
ANALYZE TABLE analyzes and stores the key
distribution for a table. During the analysis, the table is
locked with a read lock for
MyISAM. This statement works with
MyISAM tables. For
tables, this statement is equivalent to using myisamchk
--analyze. This statement does not work with views.
For more information on how the analysis works within
Section 18.104.22.168, “Configuring Persistent Optimizer Statistics Parameters” and
Section 22.214.171.124, “Estimating ANALYZE TABLE Complexity for InnoDB Tables”. Also see
Section 14.8.8, “Limits on InnoDB Tables”. In particular, when you
you must run
ANALYZE TABLE after loading
substantial data into an
InnoDB table, or
creating a new index for one.
MySQL uses the stored key distribution to decide the order in which tables should be joined when you perform a join on something other than a constant. In addition, key distributions can be used when deciding which indexes to use for a specific table within a query.
ANALYZE TABLE is supported for partitioned
tables, and you can use
ALTER TABLE ... ANALYZE
PARTITION to analyze one or more partitions; for more
information, see Section 13.1.8, “ALTER TABLE Syntax”, and
Section 22.3.4, “Maintenance of Partitions”.
In MySQL 5.7.1,
be set to
AUTOMATIC before issuing this
statement. This restriction does not apply in MySQL 5.7.2 or
later. (Bug #16062608, Bug #16715809, Bug #69045)
ANALYZE TABLE returns a result set with the
|The table name|
|An informational message|
If the table has not changed since the last
TABLE statement, the table is not analyzed again.
By default, the server writes
TABLE statements to the binary log so that they
replicate to replication slaves. To suppress logging, specify
NO_WRITE_TO_BINLOG keyword or