Re: number of cursors

Karl Hungus wrote:

 >>Per session. Raise it when you have a compelling reason to do so.
 >>Meaning you need to and the reason you need to is not poorly
 >>written code.

> Assuming the code is written well, would heavy traffic be an appropriate
> reason? Sorry if this is vague...assume a homepage requiring 2 or 3 select
> statements on a very busy site.

I bottom posted your top post.

Depends on whether more traffic means more sessions. The question is really one of whether you are a good coder and close what you open. Bad C leaks memory ... bad PL/SQL leaks cursors.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)