INF: DB-Library In Extended Stored Procedures

ID: Q115220

The information in this article applies to:

Microsoft SQL Server Programmer's Toolkit, version 4.2

SUMMARY

Execution of DB-Library (DB-Lib) calls from within an extended stored procedure is currently unsupported. Microsoft is looking into this as an area for future enhancement. In order to reliably make use of this functionality today, we recommend you implement your functions as a separate ODS application running in a separate process.

MORE INFORMATION

DB-Library makes use of several global parameters, such as query and login timeouts and the error and message handlers. These parameters are used by all threads within the current process. Since an extended stored procedure runs in the context of the SQL Server process, DB-Library calls made within the XP may interact with DB-Library calls made by SQL Server. If the functions are instead implemented in a separate ODS application and called from SQL Server using RPCs, then each application will have its own address space, eliminating any possible interactions between the function and SQL Server.

Additional query words: dblib


Keywords          : kbprg SSrvODS SSrvProg 
Version           : 4.2
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 19, 1999