CSharp Extended Stored Procedure in SQLServer 2000

[icebrrrg]

Hi. I have some functionality in a C# DLL that I would like to be able
to call from inside SQLServer. I know this was possible in C++, using
an Extended Stored Procedure, but I haven't been able to find a similar
process for C#. Does anyone know if such an animal exists?

I believe I could call the C# routines from within a C++ extended
stored procedure wrapper, but I stink as a C++ programmer (pointers?
what?) and don't want to learn C++ if at all possible. Maybe there's a
way to register a COM component in SQLServer and call the routines?

Thanks in advance for any help ...

-m-

 

[icebrrrg]

Hmm, on 2nd thought there may be no help. This tells me that I won't be
able to call on any C# (well, any CLR) code from withing SQL2k:

http://support.microsoft.com/default.aspx?scid=kb;en-us;322884

Found that link over on the sqlserver.programming group. I'd love to
find out if I'm wrong here!

-m-

 

[Octavio Hernandez]

Well, with SQL Server 2005 you'll be able to use all the C# code you want


Regards - Octavio

 

[Cletus Van Damme]

Hi. I have some functionality in a C# DLL that I would like to be able
to call from inside SQLServer. I know this was possible in C++, using
an Extended Stored Procedure, but I haven't been able to find a similar
process for C#. Does anyone know if such an animal exists?

I believe I could call the C# routines from within a C++ extended
stored procedure wrapper, but I stink as a C++ programmer (pointers?
what?) and don't want to learn C++ if at all possible. Maybe there's a
way to register a COM component in SQLServer and call the routines?

Thanks in advance for any help ...

-m-

According to Microsoft, using .Net assemblies from SQL 2000 is not
supported. However it is in fact possible...

If you register your C# DLL for use via COM then you can make use of it's
methods and properties via OLE automation extended stored procedures
(sp_OACreate, etc..). At work, we have a DLL written in C# that we use just
like this on SQL 2000. We use it for data conversion purposes, in our
development environment only, wouldn't recommend it for production.

CVD

 

[icebrrrg]

Well, with SQL Server 2005 you'll be able to use all the C# code you want

True, true. but I doubt the client wants to pay to retrain all of their
DBAs to be able to support SQL2k5 just yet. Me, I'm psyched, but
production 2k5 apps will have to wait a bit ...

-m-