Posted By: The Channel 9 Team | Jan 28th, 2005 @ 10:21 AM | 49,280 Views | 20 Comments
Milind Lele, program manager on the Visual Studio data team, shows off some of the power of the next SQL Server, code-named Yukon, when combined with the next version of Visual Studio, code-named Whidbey.

One of the big advances in the next version of SQL Server is the inclusion of the .NET Common Language Runtime. What does that mean? Well, you can build new kinds of database applications.

Milind explains it all better than we could.
Media Downloads:
Rating:
0
0

Sweet! Milind, the first Microsoft guy I ever met. Great guy, and a great interview too.

i'm glad someone finally explained when you would want to use managed code versus straight TSQL. good video.

one question, does anything need to be done on the SQL Server to enable debugging?

Thanks Chris. The connection node in server explorer has a context menu command "Enable SQLCLR debugging". You can check that to enable this. Also when you create a SQLCLR project you are prompted for a connection to use as the target for your assembly. If this is not enabled for this connection, you will be prompted to.
ZippyV
ZippyV
Fired Up
I noticed that Lele is using SqlTypes (SqlDouble). Why can't we just use the .net framework variabletypes?
nice video


could someone tell me where i can get the background Lele has on his machine?
Had read a couple of articles about the integration of CLR with Yukon but the concept was never so clear as was after watching this video.
Anyone noticed the ";" that Milind had put after a VB line of code!!! I (and may be others too) tend to do the same mistake after writing code in C# (or JAVA) for months Wink

-Aayush
Minh
Minh
WOOH! WOOH!
Very informative. Milind, could you detail the code paths of executing a native SPROC vs. a CLR SPROC? I'm mostly interested in performance issue. Whether or how much of a performance penalty a CLR SPROC may cause.
Did anyone else notice that VS .NET 2005 was running rather slow on his system?  I've seen this on my computer as well, and would really like to see a speed improvement.

Dan
I have never had an issue, what I did notice is he was running beta two LOL One can hope that is not to far off. I find that VS 2005 runs pretty quick.
Microsoft Communities