Extended Stored Procedure

Is it possible to see the contents of Extended Stored Procedure?
MadhivananIf you want to know what parameters are needed, you can do 'exec sp_help
your_xp'.
If you try to reverse engr, you could use dumpbin to disassemble the dll.
http://support.microsoft.com/kb/177429
-oj
"Madhivanan" <madhivanan2001@.gmail.com> wrote in message
news:1115442651.742719.169960@.z14g2000cwz.googlegroups.com...
> Is it possible to see the contents of Extended Stored Procedure?
> Madhivanan
>|||XP do not expose there parameter signature in any way or form, since the
function prototype of each XP is the same and the parameters are
interrogated at runtime.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23oARMQtUFHA.4092@.TK2MSFTNGP12.phx.gbl...
> If you want to know what parameters are needed, you can do 'exec sp_help
> your_xp'.
> If you try to reverse engr, you could use dumpbin to disassemble the dll.
> http://support.microsoft.com/kb/177429
> --
> -oj
>
> "Madhivanan" <madhivanan2001@.gmail.com> wrote in message
> news:1115442651.742719.169960@.z14g2000cwz.googlegroups.com...
>|||Thanks for the correction, Gert.
Look like sp_help will list @.para for regular proc but not extended proc.
Isn't there a built-in way to list the @.para for xp?
-oj
"Gert E.R. Drapers" <GertD@.SQLDevNet> wrote in message
news:eoZWVZNVFHA.1384@.TK2MSFTNGP09.phx.gbl...
> XP do not expose there parameter signature in any way or form, since the
> function prototype of each XP is the same and the parameters are
> interrogated at runtime.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2005 All rights reserved.
>|||No, this does not exist. You can not derive it from the function prototype
of an XP since they all look like:
RETCODE __declspec(dllexport) xp_foo(SRV_PROC* srvproc)
And there does not exist a mechnism for an XP to expose this information to
SQL Server. That is why it is a good practices for an XP to use a wrapper SP
to make this information available towards developers.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23mlqJsNVFHA.628@.tk2msftngp13.phx.gbl...
> Thanks for the correction, Gert.
> Look like sp_help will list @.para for regular proc but not extended proc.
> Isn't there a built-in way to list the @.para for xp?
> --
> -oj
>
> "Gert E.R. Drapers" <GertD@.SQLDevNet> wrote in message
> news:eoZWVZNVFHA.1384@.TK2MSFTNGP09.phx.gbl...
>