> My experience with stored procedures is that they help quite a bit
(performance
> wise) if you do lots of database interactions inside the stored procedure
(such as
> updating a number of related tables).
Maybe it was just our (clear ink's) PL/SQL guru that was working for us, but
our experience was just the opposite. We had a rather large stored procedure
that worked against a number of tables (this was a highly normalized
database) and we re-wrote the same code as a java method and the java code
was an order of a magnitude faster. (ie: it went from like 60+ seconds to
like 15 seconds to do exactly the same thing). I do trust that our guru's
code was good (I looked at it myself) but you never know. ;-)
On top of it, we had heard similar things from people within oracle about
the performance of pl/sql not being that great, especially under high
concurrency loads.
-jon
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
