Title: RE: Excessive SQL*Net message from client waits

I recently worked on tracing and tuning a process where developer retrieved one row, did a bunch of pl/sql stuff and update ... lather, rinse and repeat.

There were a lot of SQL*Net message from/to client. I finally opened up the procedure, found that 90% plus stuff, which was being done in pl/sql could be done in the main SQL (select statement) itself, we tested it and the developers is happy since then. It cut down a lot of wait time ... we didn't go for a bulk process as it was a lot of XML and CLOB processing involved in there.

Raj
-------------------------------------------------------------
Rajendra dot Jamadagni at espn dot com
Any views expressed here are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !!

********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may 
contain information that is privileged, attorney work product or exempt from 
disclosure under applicable law. If you have received this message in error, or are 
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 
and delete this e-mail message from your computer, Thank 
you.*********************************************************************2

Reply via email to