Connection Pooling and the data access application block

[Edward W.]

I was looking at the data access application block version 2 and considering
what I had read about connection pooling in that to use connection pooling
successfully, you should close your sqlconnections as quickly as possible.
The DAAB doesn't seem to close or dispose of connections. Are people using
the DAAB on web applications or maybe have people added to the DAAB to
close/dispose connections?

[Chris Hyde]

Edward W. wrote:

I was looking at the data access application block version 2 and considering
what I had read about connection pooling in that to use connection pooling
successfully, you should close your sqlconnections as quickly as possible.
The DAAB doesn't seem to close or dispose of connections. Are people using
the DAAB on web applications or maybe have people added to the DAAB to
close/dispose connections?

The DAAB DOES handle connections properly, when its creates the
connection itself (using the methods that take a connection string as a
parameter), and it also allows you to pass in your own connection
object. If you pass in your own connection object, you are required to
handle its opening/closing yourself.

HTH...
Chris

[Lowell Heddings]

DAAB is a really great framework... the only issue that I had with it
was the lack of a good way to handle transactions, although you can
manually do it with the ExecuteScalar function.

Yes, it does close connections properly.

Lowell

Chris Hyde wrote:

Edward W. wrote:

I was looking at the data access application block version 2 and
considering what I had read about connection pooling in that to use
connection pooling successfully, you should close your sqlconnections
as quickly as possible. The DAAB doesn't seem to close or dispose of
connections. Are people using the DAAB on web applications or maybe
have people added to the DAAB to close/dispose connections?

The DAAB DOES handle connections properly, when its creates the
connection itself (using the methods that take a connection string as a
parameter), and it also allows you to pass in your own connection
object. If you pass in your own connection object, you are required to
handle its opening/closing yourself.

HTH...
Chris

[WJ]

DAAB handles everything for you efficiently. Using DAAB also reduces bugs. I
always close my own connection, however, I check the state of connection
before closing/opening it.

John

"Edward W." <ed******@aol.comXSPAMMERIHATEYOU> wrote in message
news:OV**************@TK2MSFTNGP09.phx.gbl...

I was looking at the data access application block version 2 and
considering what I had read about connection pooling in that to use
connection pooling successfully, you should close your sqlconnections as
quickly as possible. The DAAB doesn't seem to close or dispose of
connections. Are people using the DAAB on web applications or maybe have
people added to the DAAB to close/dispose connections?

[JP.Sklenka]

I've been using DAAB since v1 and am currently using v2 and find it to be
very solid. The DAAB allows consumer to pass in a connection or transaction
object to method overloads and it's up to the consumer to close connection
(cleanup in the finally portion of try...catch block to ensure connections
are being disposed of properly).

Consuming code also has access to overloads that take a connection string -
in this instance the DAAB handles opening and closing the connection for you
(in an efficient manner). Also keep in mind that connections are pooled per
unique connection string.

"Edward W." wrote:

I was looking at the data access application block version 2 and considering
what I had read about connection pooling in that to use connection pooling
successfully, you should close your sqlconnections as quickly as possible.
The DAAB doesn't seem to close or dispose of connections. Are people using
the DAAB on web applications or maybe have people added to the DAAB to
close/dispose connections?

[HARI PRASD BARU]

DAAB is using "The using statement" which automatically calls Dispose on the
object being "used" when leaving the scope of the using statement.
For example:
//C#

string connString = "Data Source=localhost;Integrated
Security=SSPI;Initial Catalog=Northwind;";
using (SqlConnection conn = new SqlConnection(connString))
{

SqlCommand cmd = conn.CreateCommand();
cmd.CommandText = "SELECT CustomerId, CompanyName FROM Customers";
conn.Open();
using (SqlDataReader dr = cmd.ExecuteReader())
{
while (dr.Read())
Console.WriteLine("{0}\t{1}", dr.GetString(0),
dr.GetString(1));
}
}
"Edward W." wrote:

I was looking at the data access application block version 2 and considering
what I had read about connection pooling in that to use connection pooling
successfully, you should close your sqlconnections as quickly as possible.
The DAAB doesn't seem to close or dispose of connections. Are people using
the DAAB on web applications or maybe have people added to the DAAB to
close/dispose connections?