Hi,

Just to add to this topic I stumbled across a Free e-book at the veritas website http://www.veritas.com in the bottom left hand corner is a e-book on sqlserver 2000 performance tuning (sp.) 175 pages so far it looks good (it's amazing what info is out there??)

jp


>The current recommendation is to write TSQL stored procedures for intensive data-manipulation functionality and managed code for functionality that is calculation-intensive.
>
>My guess is that we'll see the use of managed code be abused in the beginning strictly because of the "neat technology" aspect of it.
>
>There's a lot of good SQL Server 2005 information at http://www.microsoft.com/sql/yukon/productinfo/
>
>-Mike
>
>
>>My understanding is that some things will still be better coded in T-SQL and others in .NET, but I haven't done any experimenting with Yukon, so others may chime in and clarify this.
>>
>>>I've been wondering about this using C# to write store procedure thing. From my understanding, it is just using a different syntax to write the same store procedure. Since most of the code in a store proc are SELECT/INSERT/UPDATE statements, I really don't see that much different. Are there other enhancements that I don't know about?