User Controls and ADO connections

[Paul]

I have 3 User Control .ascx files that are included in a base .aspx file.

In each ascx file, as well as the base aspx file, I make ADO.Net calls that
require a datatbase connection.

It appears that I have to open and close the connection in each file (i.e. I
can not reuse the open connection between all 4 pages)? This means that I
must open and close the connection 4 times when servering one page (base aspx
and 3 ascx files).

Is there any way that I can accomplish this without so opening and closing
the connection so many times?

Wouldn't this become a scalability problem if I continually have to open and
close connections multiple times on each page?

I have thought about using a session variable for the connection, but I have
read the MS does not recommend using a session variable for the connection?

TIA

[Marina]

I don't think it would be a problem. In fact, the longer you keep a
connection open, the more a scalability problem it may be, since presumably
most of that time the page is actually doing other things. So if you keep
connections open for long periods of times, when you get many users hitting
your site, there may not be enough to go around.

I would say you are doing it the right way. This is the most manageable and
maintainable, since each control can clean up after itself.

"Paul" <Pa**@discussions.microsoft.com> wrote in message
news:A9**********************************@microsof t.com...

I have 3 User Control .ascx files that are included in a base .aspx file.

In each ascx file, as well as the base aspx file, I make ADO.Net calls
that
require a datatbase connection.

It appears that I have to open and close the connection in each file (i.e.
I
can not reuse the open connection between all 4 pages)? This means that I
must open and close the connection 4 times when servering one page (base
aspx
and 3 ascx files).

Is there any way that I can accomplish this without so opening and closing
the connection so many times?

Wouldn't this become a scalability problem if I continually have to open
and
close connections multiple times on each page?

I have thought about using a session variable for the connection, but I
have
read the MS does not recommend using a session variable for the
connection?

TIA

[S. Justin Gengo]

Paul,

Marina is absolutely correct, on top of that if you're connecting to a SQL
database .NET's built in connection pooling reuses connections in the most
efficient manner automatically.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Marina" <so*****@nospam.com> wrote in message
news:eU**************@tk2msftngp13.phx.gbl...

I don't think it would be a problem. In fact, the longer you keep a
connection open, the more a scalability problem it may be, since presumably
most of that time the page is actually doing other things. So if you keep
connections open for long periods of times, when you get many users hitting
your site, there may not be enough to go around.

I would say you are doing it the right way. This is the most manageable
and maintainable, since each control can clean up after itself.

"Paul" <Pa**@discussions.microsoft.com> wrote in message
news:A9**********************************@microsof t.com...

I have 3 User Control .ascx files that are included in a base .aspx file.

In each ascx file, as well as the base aspx file, I make ADO.Net calls
that
require a datatbase connection.

It appears that I have to open and close the connection in each file
(i.e. I
can not reuse the open connection between all 4 pages)? This means that I
must open and close the connection 4 times when servering one page (base
aspx
and 3 ascx files).

Is there any way that I can accomplish this without so opening and
closing
the connection so many times?

Wouldn't this become a scalability problem if I continually have to open
and
close connections multiple times on each page?

I have thought about using a session variable for the connection, but I
have
read the MS does not recommend using a session variable for the
connection?

TIA

[Sreejith Ram]

it is adviced to keep the connection for a minimal amount of time.. so your
current approch is efficient

Following may help, "Best Practices for Using ADO.NET"

http://msdn.microsoft.com/library/en...st_topic5&_r=1

"Paul" wrote:

I have 3 User Control .ascx files that are included in a base .aspx file.

In each ascx file, as well as the base aspx file, I make ADO.Net calls that
require a datatbase connection.

It appears that I have to open and close the connection in each file (i.e. I
can not reuse the open connection between all 4 pages)? This means that I
must open and close the connection 4 times when servering one page (base aspx
and 3 ascx files).

Is there any way that I can accomplish this without so opening and closing
the connection so many times?

Wouldn't this become a scalability problem if I continually have to open and
close connections multiple times on each page?

I have thought about using a session variable for the connection, but I have
read the MS does not recommend using a session variable for the connection?

TIA