Hi

I second Don's opinion. Also, the connection pooling,
now a days is managed mostly by the Server.

Shreekar
--- Don Burr <dburr@n...> wrote:
> You opinions please.......
> 
> It seems there are two schools of thought when it
> comes to database
> connections.
> 
> 1.) Create the connection upfront when the
> application starts and hold it
> open until the application ends.
> 
> 2.) Open the connection on demand each time you need
> it
> 
> 
> I see pros and cons for both, but favor method
> number 1 (hold open for the
> duration of the app)
> 
> Pros and Cons as I see them.
> 
> 1.) Create once
> PROS
> 	Speed, no performance hit opening and closing
> connections
> 	Management, only one connection object to worry
> about
> 	Memory, no overhead associated with the constant
> creating, opening, closing
> and destroying
> CONS
> 	Holds a connection so you need more concurrent
> licenses
> 	In the event that a single process will need
> events, you must either always
> declare with events and take the performance hit or
> open with events as
> needed
> 
> 
> 
> 2.) Create on demand
> PROS
> 	Does not hog connections
> 	Can create using different methods ( i.e. Events )
> CONS
> 	Slow Slow Slow
> 
> 
> 
> 
> 
$subst('Email.Unsub').


__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/