ALTER TABLE Statement case the statement acts on all table partitions. For more information and examples, see Section 24.3.4, “Maintenance of Partitions” . InnoDB  does not currently support per-partition optimization;  ALTER TABLE ... OPTIMIZE PARTITION  causes the entire table to rebuilt and analyzed, and an appropriate warning to be issued. (Bug #11751825, Bug #42822) To work around this problem, use  ALTER TABLE ... REBUILD PARTITION  and  ALTER TABLE ... ANALYZE PARTITION  instead. The  ANALYZE PARTITION ,  CHECK PARTITION ,  OPTIMIZE PARTITION , and  REPAIR PARTITION options are not supported for tables which are not partitioned. It is possible for an  ALTER TABLE  statement to contain a  PARTITION BY  or  REMOVE PARTITIONING clause in an addition to other alter specifications, but the  PARTITION BY  or  REMOVE PARTITIONING clause must be specified last after any other specifications. The  ADD PARTITION ,  DROP PARTITION ,  COALESCE PARTITION ,  REORGANIZE PARTITION , ANALYZE PARTITION ,  CHECK PARTITION , and  REPAIR PARTITION  options cannot be combined with other alter specifications in a single  ALTER TABLE , since the options just listed act on individual partitions. For more information, see Section 13.1.9.1, “ALTER TABLE Partition Operations” . Only a single instance of any one of the following options can be used in a given  ALTER TABLE statement:  PARTITION BY ,  ADD PARTITION ,  DROP PARTITION ,  TRUNCATE PARTITION ,  EXCHANGE PARTITION ,  REORGANIZE PARTITION , or  COALESCE PARTITION ,  ANALYZE PARTITION ,  CHECK PARTITION ,  OPTIMIZE PARTITION ,  REBUILD PARTITION ,  REMOVE PARTITIONING . For example, the following two statements are invalid: In the first case, you can analyze partitions  p1  and  p2  of table  t1  concurrently using a single statement with a single  ANALYZE PARTITION  option that lists both of the partitions to be analyzed, like this: In the second case, it is not possible to perform  ANALYZE  and  CHECK  operations on different partitions of the same table concurrently. Instead, you must issue two separate statements, like this: REBUILD  operations are currently unsupported for subpartitions. The  REBUILD  keyword is expressly disallowed with subpartitions, and causes  ALTER TABLE  to fail with an error if so used. CHECK PARTITION  and  REPAIR PARTITION  operations fail when the partition to be checked or repaired contains any duplicate key errors. For more information about these statements, see Section 24.3.4, “Maintenance of Partitions” . 13.1.9.2 ALTER TABLE and Generated Columns • REMOVE PARTITIONING  enables you to remove a table’s partitioning without otherwise affecting the table or its data. This option can be combined with other  ALTER TABLE  options such as those used to add, drop, or rename columns or indexes. •Using the  ENGINE  option with  ALTER TABLE  changes the storage engine used by the table without affecting the partitioning. The target storage engine must provide its own partitioning handler. Only the InnoDB  and  NDB  storage engines have native partitioning handlers;  NDB  is not currently supported in MySQL 8.0. ALTER TABLE t1 ANALYZE PARTITION p1, ANALYZE PARTITION p2; ALTER TABLE t1 ANALYZE PARTITION p1, CHECK PARTITION p2; ALTER TABLE t1 ANALYZE PARTITION p1, p2; ALTER TABLE t1 ANALYZE PARTITION p1; ALTER TABLE t1 CHECK PARTITION p2; 2501