>Hi Markus,
>
>>
>>Yukon however hosts the CLR and can therefore be programmed in T-SQL *as well* as any .NET language.
>>
>
>Do you know if Yukon will include new libraries or data types that allow you to interact with data in a connected manner (as T-SQL does) and get better performance? I hope I'm making sense. Having OOP and heavy-duty processing capabilities in the same language would be the closest thing to VFP in my book, but I don't know if that is where they are headed with Yukon. In an interview on Channel9, someone mentioned that T-SQL should still be used for the high-performance data munging, but .NET could be used for other stuff that wasn't done best in T-SQL.

I am not sure that I am the right guy to answer this question, but I will try.

Basically, when you deploy .NET code into Yukon, things work very similar to using ADO, except of course, that there is no connection since you are already in SQL. Actual data manipulation however is still done in T-SQL. But you can code your own data types and such.

Markus