I have yet to see a good example of what can be done with the SQLCLR that can't be accomplished with some T-SQL savvy.

I think the idea of the CLR in SQL Server was one of those ideas someone brings up in a staff meeting, sounds great to management, and sounds even better to marketing.

In addition, I believe the SQLCLR is a gross violation of the DRY principle.

What's next? - the SMSCLR, the VSCLR, the POWERPOINTCLR, the COM+CLR, *8,.,

While a developer myself, I have never blamed a DBA for being territorial about the Back End. However, since technology drives new features; and vendors decide how they implement them, chances are, in the end, we will be puting up with crap in the Back End (no pun intended =).