(mysql.info.gz) Moving

Info Catalog

(mysql.info.gz) Backing up

(mysql.info.gz) InnoDB

(mysql.info.gz) InnoDB transaction model

 
 15.10 Moving an `InnoDB' Database to Another Machine
 ====================================================
 
 On Windows, `InnoDB' internally always stores database and table names
 in lowercase. To move databases in a binary format from Unix to Windows
 or from Windows to Unix, you should have all table and database names
 in lowercase. A convenient way to accomplish this on Unix is to add the
 following line to the `[mysqld]' section of your `my.cnf' before you
 start creating your databases and tables:
 
      [mysqld]
      set-variable = lower_case_table_names=1
 
 On Windows, `lower_case_table_names' is set to `1' by default.
 
 Like `MyISAM' data files, `InnoDB' data and log files are
 binary-compatible on all platforms if the floating-point number format
 on the machines is the same.  You can move an `InnoDB' database simply
 by copying all the relevant files, which were listed in  Backing
 up.  If the floating-point formats on the machines are different but
 you have not used `FLOAT' or `DOUBLE' data types in your tables, then
 the procedure is the same: Just copy the relevant files. If the formats
 are different and your tables contain floating-point data, you have to
 use `mysqldump' to dump your tables on one machine and then import the
 dump files on the other machine.
 
 A performance tip is to switch off autocommit mode when you import data
 into your database, assuming that your tablespace has enough space for
 the big rollback segment the big import transaction will generate.  Do
 the commit only after importing a whole table or a segment of a table.
 

Info Catalog

(mysql.info.gz) Backing up

(mysql.info.gz) InnoDB

(mysql.info.gz) InnoDB transaction model