Jeff Moden (9/28/2012)
XMLSQLNinja (9/28/2012)
bteraberry (9/28/2012)
Microsoft invested a huge amount of effort/time/money into CLR to give us tremendous capabilities. I have been told by someone close to the SQL dev team at MS that they are tremendously disappointed by the lack of adoption to the point they significantly curtailed planned efforts to make CLR even more robust. People like CELKO spread misinformation and outright lies about CLR to prevent more widespread adoption. Why they do such a thing is a guess, but I think it has something to do with not wanting to learn new things due to being stuck in the 80's (or 60's as the case may be.) This may seem harsh, but I think it's fantastically unwarranted to lie on a forum that's supposed to help younger developers get the truth about SQL Server.Well said.
I am by no means a Microsoft Koo-laid drinker: Microsoft does some things I don't agree with but introducing CLRs was absolutely a great move on their part.
Ok... now you have me curious. What have you written in the form of a CLR?
There is no better way to start a Saturday morning than some CLR small talk. :w00t: If I could write a CLR that helps with a mild hangover that's what I'd be doing write now.
Over the years I have written CLR's for things like: applying regex statements to a string for the purposes of data cleansing/validation. I personally prefer XSLT transforms over SQLXML so I had to write a C# CLR that transforms XML. Stuff I can't do with T-SQL. This week I wrote an F# 'hello world' CLR (I am teaching myself F#).
Again, I aver that the introduction of CLRs was one of the best things Microsoft introduced in SQL 2005. Personally I avoid them whenever possible but not for the nonsensical reasons laid out by Mr. Celco.
-- Itzik Ben-Gan 2001