應(yīng)用場景:
數(shù)據(jù)庫里有個(gè)地址(address)字段,類型為varchar(100),業(yè)務(wù)決定了要經(jīng)常根據(jù)address來進(jìn)行查詢。
確定選擇性:
Sql代碼?
SELECT count(DISTINCT(address))/count(*) AS Selectivity FROM info;???
+-------------+????
| Selectivity |???
+-------------+????
|????? 0.8745 |???
+-------------+???
選擇性很好,但是長度為100,對整個(gè)字段建立索引顯然不合適,可以考慮建立前綴索引,例如,看看其選擇性:??
Sql代碼?
SELECT count(DISTINCT(left(address,5)))/count(*) AS Selectivity FROM info;???
+-------------+????
| Selectivity |???
+-------------+????
|?0.5981 |
+-------------+????
選擇性還不錯(cuò),但和0.8745相比還是太低,所以我們可以將前綴長度增加到10,再看看選擇性:
Sql代碼?
SELECT count(DISTINCT(left(address,10)))/count(*) AS Selectivity FROM info;???
+-------------+????
| Selectivity |???
+-------------+????
|????? 0.8239 |???
+-------------+???
和0.8745已經(jīng)很接近了,但是索引長度只有10,所以就可以決定建立前綴索引了。
前綴索引兼顧索引大小和查詢速度,但是其缺點(diǎn)是不能用于ORDER BY和GROUP BY操作,也不能用于Covering index(即當(dāng)索引本身包含查詢所需全部數(shù)據(jù)時(shí),不再訪問數(shù)據(jù)文件本身)。