>Bummer, we do a lot of pre and post-processing of data sets and views and were looking to an alternative to having to perform a lot of "data over the wire" transfers while performing these. we also have lots of embedded function in our queries and are always needing one value from a data set to use in processing in some cases. We also are very dynamic in what columns are in our views and the user has total control over which ones he gets back. T-SQL is just painful when we are striving to remain abstract and data-driven.
>
>We are excited about possibly using this functionality to keeping code down over writing many static sprocs.

Viv's post just shows M@'s position on the use of the clr functionality. I read should or should not, not don't. If you need the functionality and it saves you processing time on the client, I would go for it.