http://www.sqlclr.netRSS feeds for SQLCLR.net60http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/40/QA-with-Adam-Machanic--Whos-Afraid-of-SQLCLR.aspx#Comments0http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=40http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=40&PortalID=0&TabID=54http://summit2009.sqlpass.org/Agenda/PrePostConferenceSessions/MachanicQA.aspxYou could almost hear the gasps of horror when Microsoft integrated the .NET Common Language Runtime (CLR) into SQL Server 2005. Run C# or VB.NET code inside SQL Server? For many database developers and administrators, it was like an alien had just burst through SQL Server’s midsection. But SQL Server MVP Adam Machanic says that more and more developers and DBAs are discovering that far from destroying SQL Server performance and security, SQLCLR is actually a powerful ally in solving complex business and technical problems. Read More on the PASS website..Jonathan KehayiasFri, 24 Jul 2009 15:24:00 GMTf1397696-738c-4295-afcd-943feb885714:40http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/18/Default.aspx#Comments0http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=18http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=18&PortalID=0&TabID=54http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/18/Default.aspxIf 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.Jonathan KehayiasMon, 12 May 2008 00:47:00 GMTf1397696-738c-4295-afcd-943feb885714:18http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/9/Default.aspx#Comments1http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=9http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=9&PortalID=0&TabID=54http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/9/Default.aspxWhen deploying a CLR Assembly that requires EXTERNAL_ACCESS or UNSAFE as the Permission Set you have the option of either Signing the Assembly with a strong key or setting the database to TRUSTWORTHY ON.  Microsoft's recommendation is that you sign the assembly with a strong key as a best practice.Jonathan KehayiasFri, 11 Apr 2008 04:44:00 GMTf1397696-738c-4295-afcd-943feb885714:9http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/5/Determining-When-to-Use-CLR.aspx#Comments1http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=5http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5&PortalID=0&TabID=54http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/5/Determining-When-to-Use-CLR.aspxOne of the most commonly asked questions I get from developers is, should this be done with a CLR function/procedure or in TSQL?  The addition of CLR in SQL Server brought a very powerful extension to the Database Engine.  This article will focus on providing information on how to best make the decision to use CLR or TSQL to solve a problem.Jonathan KehayiasSat, 05 Apr 2008 17:35:00 GMTf1397696-738c-4295-afcd-943feb885714:5http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/4/Single-Assembly-versus-Multiple-Assemblies.aspx#Comments0http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=4http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4&PortalID=0&TabID=54http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/4/Single-Assembly-versus-Multiple-Assemblies.aspxWhen implementing CLR in SQL Server, often times it easier for developers to use a singe assembly.  This allows them to open a single Visual Studio Solution to add to or change existing CLR.  To a DBA, this can lead to a problem with security in the database server.  Rather than having a single assembly, it is instead better to separate the code out by safety level, placing all Safe Code in a common assembly.  This helps to minimize the volume of code that has to be reviewed by the DBA to know how safe the Assembly is.Jonathan KehayiasSat, 05 Apr 2008 17:20:00 GMTf1397696-738c-4295-afcd-943feb885714:4