As you can imagine, the debate has been lively, as to whether hosting CLR sprocs, triggers, etc. in a SQL Server 2005 should be a best practice for an organization. You all know my feeling on the subject – go for it, in moderation!
Personally, I like the comment posted on April 1st at the bottom of the follow-up article:
“I have been doing this for 31 years. I came to a DBA role through a developer path. The CLR is here, it can do neat stuff, make the best of it. I sympathize with with DBAs who cannot or have never written procedural code but you will have to learn. Also management is paid to be cheap. My brother (a CPA) still uses DOS based accounting programs. (posted: 4/1/2005 8:56:48 AM)“