InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 21:34:03 GMT20http://www.sqlservercentral.com/Forums/Topic523988-386-1.aspx[quote][b]Jonathan Kehayias (6/28/2008)[/b][hr]More thn anything else, UDT's and UDF's are easily used out side of SQL. This is of great benefit for things like geocoding where the UDT is used as a typed object in the app as well. SQL 2008 implements the spatial datatypes in this manner. You can download the SDK online.[/quote]Thank you, that I didn't know...Sat, 28 Jun 2008 11:55:15 GMTMarios Philippopouloshttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxMore thn anything else, UDT's and UDF's are easily used out side of SQL. This is of great benefit for things like geocoding where the UDT is used as a typed object in the app as well. SQL 2008 implements the spatial datatypes in this manner. You can download the SDK online.Sat, 28 Jun 2008 08:20:27 GMTJonathan Kehayiashttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxFor the purposes of this debate, what is the point of invoking SQLCLR code outside a SQL context?I'm wondering if this is even necessary.What are the possible scenarios for this? If the SQLCLR assembly is accessing environmental resources (O/S, registry, event logs etc.) why can't this be done from the .NET code without using the SQLCLR? If not, what is the assembly doing?Pls everybody, humor me on this, am I missing something?Sat, 28 Jun 2008 07:10:17 GMTMarios Philippopouloshttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxIf you want to use the Logic from a CLR Stored Procedure outside of SQL Server, you need to code it for such a purpose. I generally abstract the logic portions that may be used outside of SQL Server into traditional methods and call out to those in SQL and in the application. The SqlPipe and SqlContext don't exist outside of SQL Server, so you have to code a test for them in your CLR code so that it functions properly if it is being run outside of SQL Server.Fri, 27 Jun 2008 20:17:48 GMTJonathan Kehayiashttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxhow to use this assembly in .net thenThu, 26 Jun 2008 23:07:30 GMTbhakti-sonuhttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxMake a common library that you can call both from your SQLCLR wrapper and from VB.net.Thu, 26 Jun 2008 19:49:48 GMTRBarryYounghttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxThe purpose of a SQLCLR assembly is for it to be invoked from within SQL code.You don't need to call it from .NET code.What is your assembly doing?Thu, 26 Jun 2008 10:26:13 GMTMarios Philippopouloshttp://www.sqlservercentral.com/Forums/Topic523988-386-1.aspxi have created an assembly in sql server. written stored procedures ,triggers and a function to it now tell me how can I use this assembly in VB.net to view the records or results.I tried it by using the same method as we follow for private assembly but it gives ---------------------------------Imports SqlServerProject2Dim o As StoredProcedures StoredProcedures.PrintDate()----------------------------------------an error occurs :-"The requested operation requires a SqlClr context, which is only available when running in the Sql Server process." how to resolve this?Thu, 26 Jun 2008 04:17:16 GMTbhakti-sonu