Articles

Current Articles | Categories | Search | Syndication

By Jonathan Kehayias @ Saturday, October 04, 2008 6:47 PM :: 802 Views :: 0 Comments

Microsoft Connect is the method by which the community can express what it would like to see in updates and future releases of SQL Server.  Greg Low, a SQL Server MVP, and director of SQL Down Under submitted a very compelling Connect item 265266, Add server-side compilation ability to SQL CLR which aims to remove the requirement to develop SQLCLR assemblies external to SQL Server.  Instead Greg proposes that the SQL Server be able to accept the CLR code inline with the CREATE FUNCTION/PROCEDURE/TRIGGER/AGGREGATE statements similar to the following:

CREATE PROCEDURE my_proc @par1 int,
                         @par2 int WITH
EXTERNAL LANGUAGE C#, PERMISSION_SET = EXTERNAL_ACCESS AS
using System;
using System.Data;
using System.Data.SqlClient;
...

Greg also recommends that there be the ability to catalog an assembly similar to:

CREATE ASSEMBLY myassembly FROM CLRCOMPILE('C#','code goes here')

which will make this a very readable source instead of the compiled binary that we get in the existing methodology.  If you feel that this is important, let Microsoft know by opening the link above and voting for the suggestion.

Posted @ Saturday, October 04, 2008 6:47 PM by Jonathan Kehayias
Previous Page | Next Page
Comments
Currently, there are no comments. Be the first to post one!
You must be logged in to post a comment. You can login here

Survey

Which of the following CLR objects are you currently using in SQL Server?




Submit Survey  View Results

Links


Copyright 2007 by SQLCLR.net Terms Of Use Privacy Statement
Website graphics provided by Matt Green Designs
Page generated in 0.062402 seconds.

All information and example code on this site is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from its use.

This site is in no way affiliated with Microsoft. Unless specifically stated otherwise, nothing should be construed to represent the official positions or opinions of Microsoft and/or its Employees.