My favorite thing about Yukon (by yag)

So, I’m at SeaTac Airport and I have my PASS (Professional Association for SQL Server) backpack (I did part of a keynote there this year). Someone asks me about the conference and we start talking about Yukon and Visual Studio (and yes, I feel like Scoble <g>). Anyway, one interesting question was what did I think was the key gain from adding the .NET CLR into SQL Server?

I think that while people tend to focus on things like the in-process version of ADO.NET, and moving some of their middle-tier code to the server, that’s not really the sweet spot. In my opinion, the big deal is that you can create functions that can be called from your T-SQL stored procedures. It opens up your stored procedures to a range of functions that were difficult to do in the past. As I said in my keynote, T-SQL is a great data-oriented language, and is the right way to do heavy data manipulation. The CLR languages are great at doing things like math and string manipulation. For instance, if you have to convert from hex to decimal, a CLR function is a lot easier than T-SQL. Or, if you want to use the great encryption classes from the CLR to encrypt/decrypt your data – the best way is with some VB/C# code that can be called from your T-SQL procedures.

What types of things excite you about the upcoming Yukon release?

Comments (7)

  1. Sean Terry says:

    You hit the nail on the head for me. CLR function capability is the *only* feature that will get me to fork out money for a new version of SQL Server.

  2. varbinary(max) FileStream in particular. But mainly out of curiosity.

  3. Peter says:

    Do you think that doing the SQLCLR it’s worth the effort just for writing functions more easily?

    I think moving the middle tier to SQLServer could be a very popular option for a lot of applications (perhaps not the ones with the highest scalability needs) that will have a very big improvement in performance. But that requires that MS stops saying that you need to use the CLR in SQL Server just for functions 😉

  4. Kent Tegels says:

    I agree with you and Peter, being able to able to use the best tool for the job is the best feature. I also like the XML and XQuery support.

  5. Joku says:

    I’m looking forward to fuzzy lookups and CLR integration. I have data entered from various sources by various people, and there’s so many information providers that it’s not possible to go tell them all exactly how to do it in similar manner. I hope the new fuzzy functionality will help matching similar entries into one lookup index or something.

Skip to main content