SQLCLR.nethttp://www.sqlclr.netRSS feeds for SQLCLR.net60http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/38/Default.aspx#Comments0http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=38http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=38&PortalID=0&TabID=54Trading in xp_cmdshell for SQLCLR (Part 1) - List Directory Contents http://www.sqlservercentral.com/articles/SQLCLR/65656/Learn how to use SQLCLR to get file system information instead of using xp_cmdshell on your SQL Servers.Jonathan KehayiasFri, 06 Feb 2009 17:21:00 GMTf1397696-738c-4295-afcd-943feb885714:38http://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/34/Default.aspx#Comments1http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=34http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=34&PortalID=0&TabID=54Using CLR Impersonation to Access Resources Outside of SQL Serverhttp://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/34/Default.aspxTraditionally if you had a need to access a file or other resource outside of SQL Server, the SQL Server service account was required to have appropriate file system access to the folder or path containing the file.  With CLR integration, this is no longer an absolute requirement.  Identity Impersonation will allow you to implicitly or explicitly change the execution context inside of a SQLCLR Function, Procedure, or Trigger. Jonathan KehayiasSat, 02 Aug 2008 01:35:00 GMTf1397696-738c-4295-afcd-943feb885714:34http://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=54Signing an Assembly with a Certificate (Visual Studio)http://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/8/Default.aspx#Comments0http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=54&ModuleID=371&ArticleID=8http://www.sqlclr.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=8&PortalID=0&TabID=54Setting Database Trustworthy On or Signing Assemblies with Certificateshttp://www.sqlclr.net/Articles/tabid/54/articleType/ArticleView/articleId/8/Default.aspxDetermining whether to set the Trustworthy Property of a database to ON or to sign your assembly with a certificate might be a confusing thing.  Simply searching online for how to run UNSAFE or EXTERNAL permission Assemblies in SQL Server makes it seem as if setting the Trustworthy Property to ON is the right way to go.  This however is not the Microsoft recommended practice...Jonathan KehayiasFri, 11 Apr 2008 03:35:00 GMTf1397696-738c-4295-afcd-943feb885714:8