| title | Removing an Extended Stored Procedure | ||||
|---|---|---|---|---|---|
| ms.date | 03/14/2017 | ||||
| ms.prod | sql | ||||
| ms.prod_service | database-engine | ||||
| ms.reviewer | |||||
| ms.technology | |||||
| ms.topic | reference | ||||
| helpviewer_keywords |
|
||||
| ms.assetid | 7827e574-3f59-4279-9a9b-532582e041cb | ||||
| author | rothja | ||||
| ms.author | jroth | ||||
| ms.custom | seo-dt-2019 |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
Important
[!INCLUDEssNoteDepFutureDontUse] Use CLR Integration instead.
To drop each extended stored procedure function in a user-defined extended stored procedure DLL, a [!INCLUDEssNoVersion] system administrator must run the sp_dropextendedproc system stored procedure, specifying the name of the function and the name of the DLL in which that function resides. For example, this command removes the function xp_hello, located in a DLL named xp_hello.dll, from [!INCLUDEssNoVersion]:
sp_dropextendedproc 'xp_hello'
Beginning with [!INCLUDEssVersion2005], sp_dropextendedproc does not drop system extended stored procedures. Instead, the system administrator should deny EXECUTE permission on the extended stored procedure to the public role.