Re: ADO recordsets using a stored procedure

There are solid reasons to use stored procedures to return recordsets from Oracle, and performance enhancement is one of the top reasons. You normally don't want to go through the parse, execute, and fetch steps each time you run a query, especially the exact same query is run by multiple users through the web (ASP), when you can save the parsed form of the SQL in the database. Oracle can return the result faster that way.

Lou was right on target when he said returning recordsets from Oracle through ADO is not simple. Basically you have to return multiple PL/SQL tables, one for each field selected, as output parameters from stored procedures, and piece them together to form a single recordset. To see how this actually works, check out the following article at the Microsoft Knowledge base web site.

http://support.microsoft.com/support/kb/articles/q176/0/86.asp

Hope this helps.

Eric Ma

Philippe <parnaud_at_yahoo.com> wrote in message news:7b17m7$bd3$1_at_concorde.ctp.com...
>Hi Lou,
>
>Set rs = DBCon.Execute("select * from pubs")
>
>is the simplest way, why do you need to call a procedure ?
>
>
>Lou Keeble wrote in message <7av62r$5an$1_at_hirame.wwa.com>...
>>I want to get an ADO recordset in an ASP script using a stored procedure.
>>How do I do that with Oracle?
>>
>>With SQL Server/Transact-SQL I could write:
>>
>>create procedure myproc
>>as
>>select * from pubs
>>
>>and I could get the recordset using
>>
>>Set rs = DBCon.Execute(myproc)
>>
>>With Oracle it does not appear to be so simple
>>
>>Thanks,
>>
>> -Lou Keeble
>>
>>
>>
>
>
Received on Wed Feb 24 1999 - 22:31:41 CST