Yukon Engine: CLR Integration III

Express Yourself with Managed Database Types

JCooney.NET — Mon, 31 Jan 2005 15:37:00 GMT

DAT318: SQL Server 2005 CLR Integration

Tim Sneath — Thu, 27 May 2004 04:42:00 GMT

Microsoft's TechTalk

mehraNikoo.NET — Fri, 13 Feb 2004 02:58:00 GMT

Yukon Engine: CLR Integration IV

Tim Sneath — Mon, 26 Jan 2004 20:59:00 GMT

RE: Yukon Engine: CLR Integration III

Tim Sneath — Fri, 02 Jan 2004 16:07:00 GMT

Brian, the parameter names are declared in the CREATE PROCEDURE .. AS EXTERNAL NAME statement - in exactly the same way as if the procedure itself was written in T-SQL. See http://www.sneath.org/tim/dummydata.sql.txt for the example of this. On the SQL side, you can give the parameters any name you like, so long as they match the data types of the managed code. Does that make sense? Perhaps I've not explained it well enough. Unfortunately Yukon Beta 1 is a fairly limited beta; there's still quite a lot in flux and we're not quite ready to take large quantities of beta testers' bug reports. Beta 2 is due out in the next few months and will be more generally available. I figured that if I wrote a couple of articles on the subject I could give people a general sense of what's coming. Hope this helps, Tim

RE: Yukon Engine: CLR Integration III

Brian Smith — Wed, 31 Dec 2003 16:13:00 GMT

Looking at your full procedure, it's not clear how the parameters to the managed code get translated from the SQL - i.e. does the name RowsRequired 'require' a sql parameter of @RowsRequired, or is it done by param order? brian P.S. How can I get a beta1 - the last time I looked the main yukon website indicated it was not generally available to developers.