Extended Stored Procedures

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have written an Extended Stored Procedure and it works fine. In the installation intructions it is said that you must copy the .dll to SQLServer's binn directory. Why not put it in the GAC? (and ngen it!
/Folke
 
Greets,

The extended stored procedure is a normal Win32 DLL and not a managed
DLL (at least not yet). It requires being copied to that specific folder
because that is where the engine loads extension DLLs, using the
LoadLibrary()/GetProcAddress() Win32 API functions. It doesn't require ngen
because it's already native code. It's almost similar to an ISAPI filter,
only the IIS manager allows you to specify where that DLL exists.

Regards,

Joe

Folke said:
I have written an Extended Stored Procedure and it works fine. In the
Click to expand...
installation intructions it is said that you must copy the .dll to
SQLServer's binn directory. Why not put it in the GAC? (and ngen it!)
 
Back
Top