| title | How Extended Stored Procedures Work | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/15/2017 | |
| ms.prod | sql | |
| ms.prod_service | database-engine | |
| ms.reviewer | ||
| ms.technology | ||
| ms.topic | reference | |
| helpviewer_keywords |
|
|
| ms.assetid | 6e946d8c-3268-4b59-8a1c-1637909cd701 | |
| author | rothja | |
| ms.author | jroth |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
Important
[!INCLUDEssNoteDepFutureDontUse] Use CLR Integration instead.
The process by which an extended stored procedure works is:
-
When a client executes an extended stored procedure, the request is transmitted in tabular data stream (TDS) or Simple Object Access Protocol (SOAP) format from the client application to [!INCLUDEmsCoName] [!INCLUDEssNoVersion].
-
[!INCLUDEssNoVersion] searches for the DLL associated with the extended stored procedure, and loads the DLL if it is not already loaded.
-
[!INCLUDEssNoVersion] calls the requested extended stored procedure (implemented as a function inside the DLL).
-
The extended stored procedure passes result sets and return parameters back to the server by through the Extended Stored Procedure API.