Re: PL/SQL Wrapper Costs - Lessons Learned

On 6/20/07, Peter Sylvester <peters_at_mitre.org> wrote:
>
>
> 3) Using "singleton" SQL (or procedures) to return data associated with
> individual records is another *really bad idea*, especially when you
> expect to be doing this for a lot of records. Using a client side cursor
> loop (ResultSet loop for Java folks) can result in 10X client side
> performance improvement over running many singleton select statements.
> (and 20X performance over singleton PL/SQL wrapper procs). The gains
> made here are primarily in the reduction of the quantity of database
> calls and SQL*Net traffic.
>
>

Thanks for the summary Peter.

OOP apps are inherently chatty.

DBA's are not the only admins to complain about this.

Network admins are not known to be fond of chatty apps.

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l