Data Controls

[A. Elamiri]

Hello,

I have web controls which pull information off a database. These controls
pull things like Events, and so on. Each one of these controls use different
business objects which create the connection and do all the information
quering, however they each create their own connection.

If I have multiple controls on one page it would end up in creating multiple
connections to the SQL Server DB, is it going to have a severe impact?
should I make it so that all the controls use only one Connection per page?

Thanks

 

[Mike Newton]

Hello,

I have web controls which pull information off a database. These controls
pull things like Events, and so on. Each one of these controls use different
business objects which create the connection and do all the information
quering, however they each create their own connection.

If I have multiple controls on one page it would end up in creating multiple
connections to the SQL Server DB, is it going to have a severe impact?
should I make it so that all the controls use only one Connection per page?

Thanks

IIS uses connection pooling, which takes care of this problem. The
connections between IIS and SQL Server aren't really closed, but .NET
will show them as so. If a new connection is made, one of the closed
connections is retrieved from the pool.

 

[S. Justin Gengo]

Abdellah,

Do a google search on: SQL Server Connection Pooling.

As long as your connection string for each connection is identical then Sql
Server 2000 will automatically pool connections for you.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche

 

[A. Elamiri]

Alright thanks guys