Hi,

I am trying to make a web application using C#. I need to access database in
every webpage and for that I have created new database connection each time.
This is not an efficient way at all.

Is it possible to have some kind of Global database object which we can
refer from any page? Or is there any alternate solution ?

thanks your help

Actually it is very efficient, since ADO.NET makes use of the Connection Pool 
which is specifically designed to cache connection objects (up to 100 by 
default) and provide them on demand. So, best-practices coding dictates that 
you should create and open a new Connection object just before you do your 
database work, and then close it and allow it to return to the pool 
immediately afterward.

in C#, the using (                 ) {             }  statement construct 
ensures that Close or Dispose is called automatically once the closing brace 
is reached, even if an exception is thrown.
-- Peter
Recursion: see Recursion
site:  http://www.eggheadcafe.com
unBlog:  http://petesbloggerama.blogspot.com
bogMetaFinder:    http://www.blogmetafinder.com



"Spitfire" wrote:


> Hi,
> 
> I am trying to make a web application using C#. I need to access database in
> every webpage and for that I have created new database connection each time.
> This is not an efficient way at all.
> 
> Is it possible to have some kind of Global database object which we can
> refer from any page? Or is there any alternate solution ?
> 
> thanks your help
> 

"Spitfire"  wrote in message 
news:E7E48663-233B-4361-B7A8-6830D5BADAAF@microsoft.com...


> I am trying to make a web application using C#. I need to access database 
> in
> every webpage and for that I have created new database connection each 
> time.
> This is not an efficient way at all.


Yes it is - it is *by far* the most efficient way you can do it.


> Is it possible to have some kind of Global database object which we can
> refer from any page?


This is one of the worst things you can do in ASP.NET in terms of 
performance and scalability.

ADO.NET brings you connection pooling, so you should create your connection 
at the very last moment and destroy it as soon as you no longer need it.


-- 
Mark Rae
ASP.NET MVP
http://www.markrae.net