Home All Groups Group Topic Archive Search About

Extended Stored Procedure

Author
7 May 2005 5:10 AM
Madhivanan
Is it possible to see the contents of Extended Stored Procedure?

Madhivanan

Author
7 May 2005 7:11 AM
oj
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



Show quoteHide quote
"Madhivanan" <madhivanan2***@gmail.com> wrote in message
news:1115442651.742719.169960@z14g2000cwz.googlegroups.com...
> Is it possible to see the contents of Extended Stored Procedure?
>
> Madhivanan
>
Are all your drivers up to date? click for free checkup

Author
9 May 2005 8:02 PM
Gert E.R. Drapers
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.

Ge***@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.

Show quoteHide quote
"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" <madhivanan2***@gmail.com> wrote in message
> news:1115442651.742719.169960@z14g2000cwz.googlegroups.com...
>> Is it possible to see the contents of Extended Stored Procedure?
>>
>> Madhivanan
>>
>
>
Author
9 May 2005 9:07 PM
oj
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


Show quoteHide quote
"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.
>
> Ge***@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.
>
>
Author
17 May 2005 9:21 AM
Gert E.R. Drapers
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.

Ge***@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.

Show quoteHide quote
"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...
>> 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.
>>
>> Ge***@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.
>>
>>
>
>



Post Thread options