An important part of building CLR objects for use in SQL Server is good exception management.  Part of this is raising the exception back to the calling operation so that it can be handled appropriately.  In .NET this is handled using try/catch blocks in the code, and throwing a new instance of the Exception class with a message. This article will show how to cleanup the Exception message in TSQL to show only the needed information cleanly.

This article is to demonstrate how easy it is to write a primitive CLR regular expression function with C# and SQL Server 2005.  We will solve the problem of separating numeric from nonnumeric characters. 

Sample SQLCLR user-defined aggregate for the product of a column of numbers.  There is related discussion about the SQL  alternatives to SQLCLR aggregates.  

If you choose to implement CLR User Defined Types in SQL Server, there are certain considerations that must be understood to minimize problems later on.  This article covers these considerations and how to plan for them when you are designing the UDT.

At some point you might want to Bulk Copy data from one database to another, either for archiving, or for reporting.  Whatever your reason, if you choose to implement this with CLR, there is an important gotcha that you need to be aware of.  You can not use SqlBulkCopy with the context connection.