March 11, 2005 at 10:29 am
I have read concerns about mering t-sql and the .NET CLR in sql 2005. While I'm not for replacing t-sql set operations by VB.NET I think that t-sql error handling (ERRORAISE), and especially communicating errors back to high level languages, is poor. I think the .NET "Try..Catch..Finally..." may be of use here. Do you agree? Are there any others areas that you think would be a "clear winners" for the union of these two technologies?
TIA,
Bill
March 12, 2005 at 2:16 am
Bill,
CLR stuff is an obvious winner when it comes to mathematically complicated operations. String shredding and scalar functions are just 2 areas where I envisage alot of quick wins using the CLR.
On the off-chance that you're going to PASS Europe, my colleague Christian Wade is doing a presentation on this very subject....when, where and how to use CLR integration in the data tier.
By the way, TRY...CATCH is available in the new CLR integration but FINALLY isn't (as far as I know).
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply