How to call .NET components in SQL Server

Hi,
Can any guide me, how to register .NET component in SQL Server 2000 and call
the method.
Thanks & Regards
V.EdayachandranYou cannot call a .NET component from SQL Server 2000 directly. Either you
need to use an extended stored procedure wrapper to call it or try to create
a CCW for the component and then invoke the same using sp_OA* procedures.
Remember these are NOT supported by MS though they work ...
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
"EDA" <EDA@.discussions.microsoft.com> wrote in message
news:DE695846-A575-4B0F-B4C9-E4FCBD5F559B@.microsoft.com...
> Hi,
> Can any guide me, how to register .NET component in SQL Server 2000 and
call
> the method.
> Thanks & Regards
> V.Edayachandran|||To add to Vinod's response, here's a link to an MSKB article on the subject:
http://support.microsoft.com/defaul...b;en-us;322884.
You'll have a lot more options in SQL 2005, though.
Hope this helps.
Dan Guzman
SQL Server MVP
"EDA" <EDA@.discussions.microsoft.com> wrote in message
news:DE695846-A575-4B0F-B4C9-E4FCBD5F559B@.microsoft.com...
> Hi,
> Can any guide me, how to register .NET component in SQL Server 2000 and
> call
> the method.
> Thanks & Regards
> V.Edayachandran|||"Vinod Kumar" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
news:cuadre$1f6$1@.news01.intel.com...
> You cannot call a .NET component from SQL Server 2000 directly. Either you
> need to use an extended stored procedure wrapper to call it or try to
> create
> a CCW for the component and then invoke the same using sp_OA* procedures.
While it's not supported to call .NET components directly from SQL Server,
indirect methods which don't load the CLR into the SQL Server process are
OK. So you can use the MSXML2.ServerXMLHTTP COM library to invoke a .NET
web service, or you can install your COM-Callable .NET component in COM+ as
a COM+ server application. In the first case you are loading an unmanaged
COM library in the SQL Server process, and in the second, COM is supplying
an unmanaged proxy for the SQL Server process and remoting calls over to a
COM+ process where the CLR and and your component are loaded.
David