Sure, I appreciate that you can specify params in code, however my
colleagues are lazy buggers and the idea of having to append x number of
parameters, even if I wrap this functionality in a method starts them
winging...ie for instance one of our stored procs will take 40-50 params...
Tonix wrote in message <#SqP6Aul#GA.52_at_cppssbbsa02.microsoft.com>...
>Why incur the hit if you don't have to ?
>All that needs doing is that you specify the parameters to the stored procs
>in code.
>
>Mark Bate wrote in message
><925895431.21666.0.nnrp-10.d4f0c2e2_at_news.demon.co.uk>...
>>I have been informed that using the ADO refresh method against an Oracle
>>database to query a stored procedures parameter information is very very
>>slow, does anybody out there have any real world experience
>>of what sort of hit is envolved ??
>>
>>I am thinking on the lines of a one off hit to populate an
array/collection
>>of the parameters for each stored procedure at application startup and
then
>>hold these cached rather than querying each time the SP is fired
>>
>>Any thoughts/shared experience would be appreciated..
>>
>>replys to Newsgroup and or mark.bate_at_rad-group.com
>>
>>cheers
>>
>>
>
>
Received on Wed May 05 1999 - 06:03:19 CDT
