<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx</link><description>One of the many benefits of using CLR Integration in your database applications is the availability of rich .NET Framework libraries. SQL Server provides you with a set of built-in functions that can be used in your queries but with CLR Integration you</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>OdeToCode Links For July 4</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#435323</link><pubDate>Mon, 04 Jul 2005 20:04:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:435323</guid><dc:creator>OdeToCode Links</dc:creator><description>&lt;br&gt;Here is an oldie but a goodie: Jason Antonelli describes the URL Rewriting strategies used for MSN...</description></item><item><title>re: Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#460332</link><pubDate>Sat, 03 Sep 2005 03:17:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:460332</guid><dc:creator>Chris Pritchard</dc:creator><description>Great article!!  I found it quite usefull.  Just to be picky the N of NXX can only be from 2 to 9.  800-098-3884 would be invalid as would 800-198-3884.  I used to work on a local calling area application for a phone company :)</description></item><item><title>re: Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#462894</link><pubDate>Fri, 09 Sep 2005 16:27:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:462894</guid><dc:creator>Trevor Dwyer</dc:creator><description>I found this a particularly useful example.</description></item><item><title>re: Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#500422</link><pubDate>Tue, 06 Dec 2005 11:34:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:500422</guid><dc:creator>Bug?</dc:creator><description>Isn't there a minor bug in the first example.&lt;br&gt;&lt;br&gt;  Regex.Match(matchString.TrimEnd(null)).Success;&lt;br&gt;&lt;br&gt;Suppose that then last line should have been&lt;br&gt;&lt;br&gt;  r1.Match...</description></item><item><title>re: Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#501582</link><pubDate>Thu, 08 Dec 2005 18:58:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:501582</guid><dc:creator>CraigH</dc:creator><description>Great examples and exactly what I've been looking for.  I have a question regarding whether resource usage would become a problem when using RegExOptions.Compiled flag and passing a different matchString each time.&lt;br&gt;&lt;br&gt;MSDN says the following about compiled regular expressions.&lt;br&gt;&lt;br&gt;&amp;quot;However, generated MSIL cannot be unloaded. The only way to unload code is to unload an entire application domain (that is, to unload all of your application's code.). Effectively, once a regular expression is compiled with the RegexOptions.Compiled option, the .NET Framework never releases the resources used by the compiled expression, even if the Regex object itself is released to garbage collection.&amp;quot;</description></item><item><title>re: Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#608019</link><pubDate>Fri, 26 May 2006 17:14:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:608019</guid><dc:creator>Balaji Ramachandran</dc:creator><description>I have been thinking of moving our regular expression matching process to SQL server and I found this article very useful on that.</description></item><item><title>re: Working with Regular Expressions</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#685637</link><pubDate>Tue, 01 Aug 2006 23:50:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:685637</guid><dc:creator>Tyler</dc:creator><description>Just trying to get this going but I don't know mcuh about CLR or UDF's. &amp;nbsp;Any advice on how I can get a CLR to work that allows me to search a table of regular expressions and find the record that matches the dynamically provided input value?&lt;br&gt;&lt;br&gt;Thanks!</description></item><item><title>Complex Expression Matching within SQL Server 2005</title><link>http://blogs.msdn.com/sqlclr/archive/2005/06/29/regex.aspx#8338280</link><pubDate>Wed, 26 Mar 2008 22:06:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8338280</guid><dc:creator>SQL Server</dc:creator><description>&lt;p&gt;As it stands today complex expression matching within SQL Server 2005 is &amp;quot;possible&amp;quot; at best and a nightmare&lt;/p&gt;
</description></item></channel></rss>