之前曾有一篇POST是關(guān)于用CTE實(shí)現(xiàn)Split，這種方法已經(jīng)比傳統(tǒng)的方法高效了。今天我們就這個(gè)方法與CLR實(shí)現(xiàn)的Split做比較。在CLR實(shí)現(xiàn)Split函數(shù)的確很簡(jiǎn)單，dotnet framework本身就有這個(gè)function了。

我們新建一個(gè)DataBase project，然后建立一個(gè)UserDefinedFunctions,Code像這樣:

復(fù)制代碼代碼如下:

 
1: /// <summary> 
/// SQLs the array. 
/// </summary> 
/// <param name="str">The STR.</param> 
/// <param name="delimiter">The delimiter.</param> 
/// <returns></returns> 
/// 1/8/2010 2:41 PM author: v-pliu 
[SqlFunction(Name = "CLR_Split", 
FillRowMethodName = "FillRow", 
TableDefinition = "id nvarchar(10)")] 
public static IEnumerable SqlArray(SqlString str, SqlChars delimiter) 
{ 
if (delimiter.Length == 0) 
return new string[1] { str.Value }; 
return str.Value.Split(delimiter[0]); 
} 
/// <summary> 
/// Fills the row. 
/// </summary> 
/// <param name="row">The row.</param> 
/// <param name="str">The STR.</param> 
/// 1/8/2010 2:41 PM author: v-pliu 
public static void FillRow(object row, out SqlString str) 
{ 
str = new SqlString((string)row); 
} 

然后Bulid,Deploy一切OK后，在SSMS中執(zhí)行以下測(cè)試T-sql:

復(fù)制代碼代碼如下:

 
DECLARE @array VARCHAR(max) 
SET @array = '39,15,93,68,64,43,90,58,39,9,26,26,89,47,91,57,98,16,55,9,63,29,69,16,41,76,34,60,68,64,61,53,32,30,11,72,57,63,36,43,22,14,60,38,24,5,66,26,26,21,22,99,55,18,7,10,46,76,27,88,9,29,89,75,48,72,94,59,35,19,0,35,79,11,87,49,68,30,91,35,9,7,34,47,41,61,98,13,22,1,26,80,35,48,34,92,24,85,90,51' SELECT id FROM dbo.CLR_Split(@array,',') 

我們來看它的Client Statistic:

接著我們執(zhí)行測(cè)試T-sql使用相同的array:

復(fù)制代碼代碼如下:

 
DECLARE @array VARCHAR(max) 
SET @array = '39,15,93,68,64,43,90,58,39,9,26,26,89,47,91,57,98,16,55,9,63,29,69,16,41,76,34,60,68,64,61,53,32,30,11,72,57,63,36,43,22,14,60,38,24,5,66,26,26,21,22,99,55,18,7,10,46,76,27,88,9,29,89,75,48,72,94,59,35,19,0,35,79,11,87,49,68,30,91,35,9,7,34,47,41,61,98,13,22,1,26,80,35,48,34,92,24,85,90,51' 
SELECT item FROM strToTable(@array,',') 

CTE實(shí)現(xiàn)的Split function的Client statistic: