With April CTP came the new combined managed provider replaces System.Data.SqlServer with a new improved, works in-process or out, System.Data.SqlClient. I just call it “the combined provider” now. People that didn’t work on the betas will look at me funny when the product RTMs; “was there ever anything other than System.Data.SqlClient?”. Why yes, Virginia…<\/p>\n
With the new provider, some of the error handling problems passing SQLCLR errors back to T-SQL resurfaced. Some work-arounds didn’t work-around the same way. Some people noticed this on the newsgroups. I reported a bug on first day, but didn’t want to be too “complain-y” here. And noticed what work-arounds (AKA coding practices so\u00a0that things work right)\u00a0still work.<\/p>\n
The most severe problem was that if you tried to catch a SQLCLR error with a dummy try-catch block in your CLR code, AND executed your SQLCLR code inside a T-SQL TRY-CATCH, you got:<\/p>\n
Msg 0, Level 11, State 0, Line 0
\nA severe error occurred on the current command. The results, if any,
\nshould be discarded.<\/p>\n
Oh. That was in SSMS. In SQLCMD you got nothing. No error from the CATCH, no results.<\/p>\n
Bug is reported as fixed today. Cool. Although it was the fourth CTP after beta2, this was first *ever* release of the combined provider. They’ll iron it out. Can’t wait to try it in next CTP. Then I’ll write about it.<\/p>\n