zoukankan      html  css  js  c++  java
  • SQLSERVER2008中CTE的Split与CLR的性能比较

         之前曾有一篇POST是关于用CTE实现Split,这种方法已经比传统的方法高效了。今天我们就这个方法与CLR实现的Split做比较。在CLR实现Split函数的确很简单,dotnet framework本身就有这个function了。
        我们新建一个DataBase project,然后建立一个UserDefinedFunctions,Code像这样:

       1:      /// <summary>
       2:      /// SQLs the array.
       3:      /// </summary>
       4:      /// <param name="str">The STR.</param>
       5:      /// <param name="delimiter">The delimiter.</param>
       6:      /// <returns></returns>
       7:      /// 1/8/2010  2:41 PM   author: v-pliu
       8:      [SqlFunction(Name = "CLR_Split",
       9:      FillRowMethodName = "FillRow",
      10:      TableDefinition = "id nvarchar(10)")]
      11:   
      12:      public static IEnumerable SqlArray(SqlString str, SqlChars delimiter)
      13:      {
      14:          if (delimiter.Length == 0)
      15:              return new string[1] { str.Value };
      16:          return str.Value.Split(delimiter[0]);
      17:      }
      18:   
      19:      /// <summary>
      20:      /// Fills the row.
      21:      /// </summary>
      22:      /// <param name="row">The row.</param>
      23:      /// <param name="str">The STR.</param>
      24:      /// 1/8/2010  2:41 PM   author: v-pliu
      25:      public static void FillRow(object row, out SqlString str)
      26:      {
      27:          str = new SqlString((string)row);
      28:      }


    然后Bulid,Deploy一切OK后,在SSMS中执行以下测试T-sql:

       1:  DECLARE @array VARCHAR(max)
       2:  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'
       3:  SELECT id FROM dbo.CLR_Split(@array,',')
     

    我们来看它的Client Statistic:

    CLRSplit

    接着我们执行测试T-sql使用相同的array:

       1:  DECLARE @array VARCHAR(max)
       2:  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'
       3:  SELECT item FROM strToTable(@array,',')

    CTE实现的Split function的Client statistic:

    CTESplit

    通过对比,你可以发现CLR的performance略高于CTE方式,原因在于CLR方式有Cache功能,并且把一个复杂的运算放到程序里比DataBase里更加高效。

    您还可以参考:

    Split string in SQL Server 2005+ CLR vs. T-SQL

    Author:Petter Liu    http://wintersun.cnblogs.com

    希望这篇POST对您有帮助。

  • 相关阅读:
    修改CentOS的yum源为国内yum镜像源
    CentOS7利用yum安装node.js
    Ansible系列(一):安装
    动态链接库引起的yum故障
    《C++ Templates: The Complete Guide》读书笔记
    Linux下编译clang、libcxx及其相关库——C++11环境搭建
    shell小工具:findstr 和 findfile
    关于newexpression、new operator、operator delete的总结
    Makefile编写示例:构建一个库
    无计划就不行动!
  • 原文地址:https://www.cnblogs.com/wintersun/p/1642265.html
Copyright © 2011-2022 走看看