|
|
Posted by Dan Guzman on 11/24/07 14:52
> The DLL was written in Cobol. The "Other-Server" in the Path above is
> the server that Cobol (and the DLL) is located on.
Not just any DLL can run as a SQL Server extended stored procedure.
Extended stored procedures are usually written in C/C++, although I've heard
that some have been written using Delphi. See Creating Extended Stored
Procedures in the Books Online for details.
Separately, COM DLLs can be invoked using sp_OA* procs.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Jim" <jshain@datamann.com> wrote in message
news:8d9db5fa-a277-400f-9761-7886f9607c55@g21g2000hsh.googlegroups.com...
>
> Hi,
>
> I have a DLL that I want to run from the Query Analyzer. I tried the
> following:
>
> USE master;
> EXEC sp_addextendedproc BLAH, '\\Other-Server\Path\To\Blah\Blah.dll'
>
> and I get the error:
>
> ODBC: Msg 0, Level 16, State 1
> Cannot load the DLL \\Other-Server\Path\To\Blah\Blah.dll, or one of
> the DLLs it references. Reason: 126(The specified module could not be
> found.).
>
> The DLL was written in Cobol. The "Other-Server" in the Path above is
> the server that Cobol (and the DLL) is located on.
>
> I looked at the dependencies for the DLL and it includes (not
> surprisingly) Cobol Dll's. It should find those on the other server.
>
> What can I do?
>
> Thanks!
>
>
>
>
Navigation:
[Reply to this message]
|