The CLR in SQL Server is not meant to totally replace T-SQL. There are many cases where T-SLQ will out perform CLR procs.


>I have been playing with the capability of writing stored procedures and functions in C# and deploying them to the Sql Server 2005. This is pretty cool because I have a disdain for T-SQL outside of query syntax, but I have a question.
>
>I see that you have the ability to utilize arrays, .Net classes and such ( non-UI stuff ) in the assembly that you otherwise cannot use in T-SQL but I was wondering if you have access to all the functionality C# has to offer like generics, delegates, and so on? By what I have read and toyed with so far I think the answer is yes.
>
>Can I assume you are only hamstrung by the limitations you face in the debugging of the assembly at run-time? Depending on how complex you want to be I would think you could basically move tons of your business logic to the server and run it there, where as before we were returning datasets to the middle and performing further manipulations that we found easier to do in Fox/C# .
>
>Anyone know of some severe limitations that would keep you from using this feature fully?
>
>Michael