Tables InnoDB  files require more care and planning than  MyISAM  files do. •You must not delete the ibdata files that represent the  InnoDB  system tablespace. •Methods of moving or copying  InnoDB  tables to a different server are described in Section 15.6.1.4, “Moving or Copying InnoDB Tables” . 15.6.1.6 AUTO_INCREMENT Handling in InnoDB InnoDB  provides a configurable locking mechanism that can significantly improve scalability and performance of SQL statements that add rows to tables with  AUTO_INCREMENT  columns. To use the AUTO_INCREMENT  mechanism with an  InnoDB  table, an  AUTO_INCREMENT  column must be defined as part of an index such that it is possible to perform the equivalent of an indexed  SELECT MAX( ai_col ) lookup on the table to obtain the maximum column value. Typically, this is achieved by making the AUTO_INCREMENT  column the first column of some table index. This section describes the  AUTO_INCREMENT  lock modes, usage implications of different AUTO_INCREMENT  lock mode settings, and how  InnoDB  initializes the  AUTO_INCREMENT  counter. •InnoDB AUTO_INCREMENT Lock Modes •InnoDB AUTO_INCREMENT Lock Mode Usage Implications •InnoDB AUTO_INCREMENT Counter Initialization •Notes This section describes the  AUTO_INCREMENT  lock modes used to generate auto-increment values, and how each lock mode affects replication. The auto-increment lock mode is configured at startup using the innodb_autoinc_lock_mode  variable. The following terms are used in describing  innodb_autoinc_lock_mode  settings: InnoDB AUTO_INCREMENT Lock Modes •“ INSERT -like”  statements •“Simple inserts” •“Bulk inserts” •“Mixed-mode inserts” All statements that generate new rows in a table, including  INSERT ,  INSERT ... SELECT ,  REPLACE , REPLACE ... SELECT , and  LOAD DATA . Includes “simple-inserts” , “bulk-inserts” , and “mixed-mode” inserts. Statements for which the number of rows to be inserted can be determined in advance (when the statement is initially processed). This includes single-row and multiple-row  INSERT  and  REPLACE statements that do not have a nested subquery, but not  INSERT ... ON DUPLICATE KEY UPDATE . Statements for which the number of rows to be inserted (and the number of required auto-increment values) is not known in advance. This includes  INSERT ... SELECT ,  REPLACE ... SELECT , and LOAD DATA  statements, but not plain  INSERT .  InnoDB  assigns new values for the  AUTO_INCREMENT column one at a time as each row is processed. These are “simple insert”  statements that specify the auto-increment value for some (but not all) of the new rows. An example follows, where  c1  is an  AUTO_INCREMENT  column of table  t1 : INSERT INTO t1 (c1,c2) VALUES (1,’a’), (NULL,’b’), (5,’c’), (NULL,’d’); 3034