1.1. 優化實戰
1.1.1. 策略1.盡量全值匹配
CREATE TABLE `staffs`(
id int primary key auto_increment,
name varchar(24) not null default "" comment'姓名',
age int not null default 0 comment '年齡',
pos varchar(20) not null default "" comment'職位',
add_time timestamp not null default current_timestamp comment '入職時間'
)charset utf8 comment '員工記錄表';
insert into staffs(name,age,pos,add_time) values('z3',22,'manage',now());
insert into staffs(name,age,pos,add_time) values('july',23,'dev',now());
insert into staffs(name,age,pos,add_time) values('2000',23,'dev',now());
alter table staffs add index idx_staffs_nameAgePos(name,age,pos);
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July';
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' AND age = 25;
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' AND age = 25 AND pos = 'dev'
當建立了索引列后，能在wherel條件中使用索引的盡量所用。
1.1.2. 策略2.最佳左前綴法則
如果索引了多列，要遵守最左前綴法則。指的是查詢從索引的最左前列開始並且不跳過索引中的列。
EXPLAIN SELECT * FROM staffs WHERE age = 25 AND pos = 'dev'
EXPLAIN SELECT * FROM staffs WHERE pos = 'dev'
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July'
1.1.3. 策略3.不在索引列上做任何操作
不在索引列上做任何操作（計算、函數、(自動or手動)類型轉換），會導致索引失效而轉向全表掃描
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July';
EXPLAIN SELECT * FROM staffs WHERE left(NAME,4) = 'July';
1.1.4. 策略4.范圍條件放最后
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' ;
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' and age =22;
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' and age =22 and pos='manager'
中間有范圍查詢會導致后面的索引列全部失效
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' and age >22 and pos='manager'
1.1.5. 策略5.覆蓋索引盡量用
盡量使用覆蓋索引(只訪問索引的查詢(索引列和查詢列一致))，減少select *
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' and age =22 and pos='manager'
EXPLAIN SELECT name,age,pos FROM staffs WHERE NAME = 'July' and age =22 and pos='manager'
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July' and age >22 and pos='manager'
EXPLAIN SELECT name,age,pos FROM staffs WHERE NAME = 'July' and age >22 and pos='manager'
1.1.6. 策略6.不等於要甚用
mysql 在使用不等於(!= 或者<>)的時候無法使用索引會導致全表掃描
EXPLAIN SELECT * FROM staffs WHERE NAME = 'July';
EXPLAIN SELECT * FROM staffs WHERE NAME != 'July';
EXPLAIN SELECT * FROM staffs WHERE NAME <> 'July';
如果定要需要使用不等於,請用覆蓋索引
EXPLAIN SELECT name,age,pos FROM staffs WHERE NAME != 'July';
EXPLAIN SELECT name,age,pos FROM staffs WHERE NAME <> 'July';
1.1.7. 策略7.Null/Not 有影響
注意null/not null對索引的可能影響
1.1.7.1. 自定定義為NOT NULL
EXPLAIN select * from staffs where name is null
EXPLAIN select * from staffs where name is not null
在字段為not null的情況下，使用is null 或 is not null 會導致索引失效
解決方式：覆蓋索引
EXPLAIN select name,age,pos from staffs where name is not null
1.1.7.2. 自定義為NULL或者不定義
EXPLAIN select * from staffs2 where name is null
EXPLAIN select * from staffs2 where name is not null
Is not null 的情況會導致索引失效
解決方式：覆蓋索引
EXPLAIN select name,age,pos from staffs where name is not null
1.1.8. 策略8.Like查詢要當心
like以通配符開頭('%abc...')mysql索引失效會變成全表掃描的操作
EXPLAIN select * from staffs where name ='july'
EXPLAIN select * from staffs where name like '%july%'
EXPLAIN select * from staffs where name like '%july'
EXPLAIN select * from staffs where name like 'july%'
解決方式：覆蓋索引
EXPLAIN select name,age,pos from staffs where name like '%july%'
1.1.9. 策略9.字符類型加引號
字符串不加單引號索引失效
EXPLAIN select * from staffs where name = 917
解決方式：覆蓋索引
EXPLAIN select name,age,pos from staffs where name = 917
解決方式：請加引號
1.1.10. 策略10.OR改UNION效率高
EXPLAIN
select * from staffs where name='July' or name = 'z3'
EXPLAIN
select * from staffs where name='July'
UNION
select * from staffs where name = 'z3'
解決方式：覆蓋索引
EXPLAIN
select name,age from staffs where name='July' or name = 'z3'
1.1.11. 例子
答案：
記憶總結：
l 全職匹配我最愛，最左前綴要遵守；
l 帶頭大哥不能死，中間兄弟不能斷；
l 索引列上少計算，范圍之后全失效；
l LIKE百分寫最右，覆蓋索引不寫*；
l 不等空值還有OR，索引影響要注意；
l VAR引號不可丟， SQL優化有訣竅。
1.2. 批量導入
1.2.1. insert語句優化；
l 提交前關閉自動提交
l 盡量使用批量insert語句
l 可以使用MyISAM存儲引擎
1.2.2. LOAD DATA INFLIE
LOAD DATA INFLIE；
使用LOAD DATA INFLIE ,比一般的insert語句快20倍
select * into OUTFILE 'D:\\product.txt' from product_info
load data INFILE 'D:\\product.txt' into table product_info
load data INFILE '/soft/product3.txt' into table product_info
查看當前數據庫是否支持load data方式導入導出：
show VARIABLES like 'secure_file_priv'
解釋：
l secure_file_priv 為 NULL 時，表示限制mysqld不允許導入或導出。
l secure_file_priv 為 /tmp 時，表示限制mysqld只能在/tmp目錄中執行導入導出，其他目錄不能執行。
l secure_file_priv 沒有值時，表示不限制mysqld在任意目錄的導入導出。
配置當前數據庫支持load data方式導入導出：
在my.ini文件中添加：secure_file_priv=''