On 10/16/07, Ben Joyce <[EMAIL PROTECTED]> wrote: > > Regarding ASP.NET, I'm of the school of thought that database > connections be created at function level; as in, created and destroyed > many many times (if necessary) throughout the page life-cycle. > > Just out of interest, is there *any* situation of school of thought > where a single application-level connection to the database would be > better?
I think most people acknowledge that setting up and tearing down database connections can be very expensive -- which is why they enable connection pooling and don't worry about that in their application code. -- Curt Hagenlocher [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
