遷移phpstudy中的mysql至Linux

項目目的

將原來windows環境中使用phpstudy搭建的mysql 5.5.53 中的數據遷移至新主機Linux環境中

環境狀況

新主機
系統平臺：
CentOS release 7.4 (Final)             內核  3.10.0-693.el7.x86_64

mysql環境：
mysql> status
Server version:     5.6.39-log MySQL Community Server (GPL)
Server characterset:    utf8
Db     characterset:    utf8
Client characterset:    utf8
Conn.  characterset:    utf8

mysql> show variables like '%storage_engine%';
+----------------------------+--------+
| Variable_name              | Value  |
+----------------------------+--------+
| default_storage_engine     | InnoDB |
| default_tmp_storage_engine | InnoDB |
| storage_engine             | InnoDB |
+----------------------------+--------+

舊主機：
系統平臺：
Windows 2012 R2 SE X64

mysql環境：
Server version:         5.5.53 MySQL Community Server (GPL)
Server characterset:    utf8
Db     characterset:    utf8
Client characterset:    utf8
Conn.  characterset:    utf8

mysql> show variables like '%storage_engine%';
+------------------------+--------+
| Variable_name          | Value  |
+------------------------+--------+
| default_storage_engine | MyISAM |
| storage_engine         | MyISAM |
+------------------------+--------+

表的存儲引擎
mysql> show table status from database\G;

Engine: InnoDB
Engine: MyISAM

遷移過程

1.使用phpstudy自帶的工具進行每一個數據庫導出

我看了，也是用的mysqldump操做的。

2.若是隻是保留本來的表引擎，那麼直接如下操做便可

mysql> create database zentao;
mysql> use zentao;
mysql> source zentao20180413161534.sql;
mysql> show tables;
+-------------------+
| Tables_in_zentao  |
+-------------------+
| zt_action         |
| zt_bug            |
| zt_build          |
...

原表引擎保持原樣。
mysql> show table status from zentao\G;
*************************** 1. row ***************************
           Name: zt_action
         Engine: MyISAM
        Version: 10
     Row_format: Dynamic

3.將原有數據庫中的表引擎變動爲InnoDB

在導出的表結構zentao.sql中找到ENGINE=MyISAM,修改爲ENGINE=InnoDB,至於你用什麼方法替換，看你喜歡了。

# vim zentao.sql
:%s/ENGINE=MyISAM/ENGINE=InnoDB/g

4.導入數據到指定數據庫

mysql> use zentao;
mysql> source zentao.sql;
表引擎變動爲InnoDB
mysql> show table status from zentao\G;
*************************** 1. row ***************************
           Name: zt_action
         Engine: InnoDB
        Version: 10
     Row_format: Compact

5.可是有一個問題，查看錶的詳細信息時發現Data_free不爲零，說明存在數據碎片，須要進行優化

mysql> select table_schema, table_name, data_free, engine from information_schema.tables where table_schema not in ('information_schema', 'mysql') and data_free != 0; 
+--------------+------------+-----------+--------+
| table_schema | table_name | data_free | engine |
+--------------+------------+-----------+--------+
| zentao       | zt_bug     |   4194304 | InnoDB |
| zentao       | zt_history |   4194304 | InnoDB |
+--------------+------------+-----------+--------+

6.整理有碎片的表

mysql> use zentao;
mysql> optimize table zt_bug,zt_history;
+-------------------+----------+----------+-------------------------------------------------------------------+
| Table             | Op       | Msg_type | Msg_text                                                          |
+-------------------+----------+----------+-------------------------------------------------------------------+
| zentao.zt_bug     | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| zentao.zt_bug     | optimize | status   | OK                                                                |
| zentao.zt_history | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| zentao.zt_history | optimize | status   | OK                                                                |
+-------------------+----------+----------+-------------------------------------------------------------------+
提示該表不支持 optimize,可是下邊有顯示OK.其實已經執行成功了。5.6.X的版本，其實已經支持Innodb了

mysql> select table_name,engine,table_rows,data_length+index_length length,DATA_FREE from information_schema.tables where TABLE_SCHEMA='zentao' and data_free =0;
+-------------------+--------+------------+---------+-----------+
| table_name        | engine | table_rows | length  | DATA_FREE |
+-------------------+--------+------------+---------+-----------+
| zt_bug            | InnoDB |       1018 | 1589248 |         0 |
| zt_history        | InnoDB |       2584 | 1589248 |         0 |

多個數據庫方法一樣操做便可。