Re: Which one is better 1 connection lots of open cursors - more connections less open cursors

"Jim Kennedy" <kennedy-down_with_spammers_at_attbi.com> wrote in message news:975za.695940$Zo.149622_at_sccrnsc03...
> All cursors on one connection. If you start putting cursors on different
> connections you have the time of starting a new connection. Also with
> multiple connections you run into the problem of how to handle the
different
> transactions that each connection is on. One connection might not see an
> update another one did, whereas they currently do since they are on one
> connection.
> Jim

<snip>

If it is a J2EE application, the connections are created during server startup which minimizes the creation concern. This assumes you have profiled your application and projected user load and sized your JDBC pools accordingly.

That being said, there still is overhead in relation to maintaining the open connection with a J2EE server. As long as your application releases the cursors correctly, you should see little problems, otherwise, you run the risk of transaction rollbacks and oracle failures from "too many open cursors".

ken k Received on Thu May 22 2003 - 10:48:45 CDT