The site is currently in read-only mode for maintenance. Posting of new items will be available again shortly.
CLR Hosting is one of the new cool features of SQL Server 2005, and if used properly can greatly enhance our daily database needs.
For a better understanding of CLR Hosting in Microsoft SQL Server 2005, please visit this link.
In the early days of SQL Server (before Microsoft SQL Server 2005), writing User Defined Functions for various utility subroutines was nothing but a nightmare to developers, without having a very sound knowledge of TSQL. Now with the introduction of CLR Hosting feature in Microsoft SQL Server 2005, we can harness these types of subroutine with the help of reach .NET Base Class Library. We can create feature rich assemblies and subroutines which we can deploy seamlessly in any SQL Server 2005 database around our enterprise and can leverage the strength of these subroutines to solve our day to day TSQL programming challenges.
In this article, I've created a custom library with some UDF, which can be easily used by TSQL programmers and developers to do some very common TSQL string related tasks. The following is the task list which can be done by using this library:
- Validating a string against a string pattern (say for example an email address in the former email@example.com)
- Validating a string against some predefined string patterns (which I've supplied for day to day work, so you didn't need to reinvent the patterns), like
- Split a string with a supplied delimiter and return a custom table with
Data for easy iteration.
These are some of the very basic and straight forward aspects of this library, but if wisely used can really ease our life a lot.
Using the Code
The first and easiest way to make a jump start is to download the code and to deploy it in a test database in a Microsoft SQL Server 2005 instance. Here I'm not going into the tit bits of hosting assembly in SQL Server 2005, rather I feel better to dig down the code a bit. (The first link will provide you with a lot of resources for deployment and security issues.)
Now, going to the first method and the most easy one:
2.public static bool IsValidStringFormat_Custom(string InputString, string Pattern)
4. Regex expression = new Regex(Pattern);
5. return expression.IsMatch(InputString);
The first line of the code is an attribute which clearly dictates that the following method is nothing but a SQL function. This is really cool and really quite self explanatory. If we want any method which needs to be exposed as User Defined Function, we just need to tag it with the attribute.
In this function, we are using the .NET Framework class
System.Text.RegularExpressions.Regx for making a match with the custom provided pattern.
This utility method returns bit when invoked from SQL Server 2005, so it becomes quite easy to make a decision whether a string matches with a given pattern. It can be easily used with check constraints or Stored Procedures or inside any other User Defined Function.
The next one is the function with predefined patterns (something like our old regular expression validator with some predefined set of patterns).
public static bool IsValidFormat(string InputString, string PatternType)
bool flag = false;
flag = IsValidStringFormat_Custom(InputString, EmaiFormat);
flag = IsValidStringFormat_Custom(InputString, FrenchPhoneNo);
flag = IsValidStringFormat_Custom(InputString, FrenchPostalCode);
flag = IsValidStringFormat_Custom(InputString, GermanPhoneNo);
flag = IsValidStringFormat_Custom(InputString, GermanPostalCode);
flag = IsValidStringFormat_Custom(InputString, InternetURL);
flag = IsValidStringFormat_Custom(InputString, JapanesePhoneNo);
flag = IsValidStringFormat_Custom(InputString, JapanesePostalCode);
flag = IsValidStringFormat_Custom(InputString, PRCPhoneNo);
flag = IsValidStringFormat_Custom(InputString, PRCPostalCode);
flag = IsValidStringFormat_Custom(InputString, PRCSocialSecurityNo);
flag = IsValidStringFormat_Custom(InputString, USPhoneNo);
flag = IsValidStringFormat_Custom(InputString, USSocialSecurityNo);
flag = IsValidStringFormat_Custom(InputString, USZipCode);
There is nothing fancy about this code. I've just used some constant string pattern, and depending upon the supplied
PatternType (say for example '
USZIPCODE') matching the pattern using my old
Now going to the last function (which is a bit untidy now). This function splits a string by a given deliminator and returns a table.
[SqlFunction(FillRowMethodName = "FillRow",
TableDefinition = "Data NVARCHAR(MAX), RowNo int")]
public static System.Collections.IEnumerable Split
(SqlString InputString, string deliminator)
string strArray = InputString.Value.Split(deliminator.ToCharArray());
for (int foo = 0; foo < strArray.Length; foo++)
strArray[foo] = strArray[foo] + "~" + foo.ToString();
public static void FillRow(object row, out string str, out int RowNo)
str = (((string)row).Split('~'));
RowNo = int.Parse((((string)row).Split('~')));
The most interesting feature is that this User Defined Function returns a table rather than a bit. To accomplish this, we have use two routines, the first one
Split is the subroutine which returns
IEnumerable (which makes it enumerable just like any other data structure in
System.Collection) and the second function actually fills the table.
In the attribute declaration point, we can also see some very interesting parameters,
FillMethodName points to the method which actually fills the table which needs to be returned from the User Defined Datatype.
TableDefinition defines the actual table structure which is returned by the UDF.
Points of Interest
With the integration of CLR Hosting in SQL Server 2005, Microsoft has shown a promising integration of BCL and SQL Server DataBase which was really missing till date. If properly utilized, this can really help our day to day tough TSQL queries to run and manage in a very efficient way.
Like any other library, the most interesting part of this library is that it can be deployed and used in any SQL Server 2005 database without dependency, and there is a single point of deployment and maintenance.
- 3rd August, 2009: Initial post