There is already an open DataReader associated with this Command..

[=?Utf-8?B?QXNhZg==?=]

Hello,

I have two Table Adapters that I am storing in a Cache using .NET 2.0 Web
Service and the Database is SQL Server on Windows 2003 IIS6.
Each of the two table adapters has its own Connection string.

The reason that table adapters are in cache is because I would like to
maintain the connection string that will not be closed for any Insert or
Update as there are thousands of requests per minutes to the WS.

Problems are that when calling Insert or Update from the table adapters I
received the error:
"There is already an open DataReader associated with this Command which must
be closed first" and then the table adapter that I called Insert or Update
from is remove from the Cache.
Thanks in advanced for any advice.
Asaf

[Spam Catcher]

"Mr. Arnold" <MR. Ar****@Arnold.c omwrote in
news:eT******** ******@TK2MSFTN GP02.phx.gbl:

Well #1, I wouldn't be using Table Adapters in a solution myself. I
would be using SQL Command Objects with a Stored Procedure, which is
a faster solution, because it would be a precompiled Stored Procedure
that will stay in memory based on the traffic you indicate.

As a note, it's a religious debate between inline SQL and stored
procedures. As far as I'm aware, the performance gain by using SPs is
minimal, hence I prefer to use inline SQL (no need to load SQL onto a
server, and everything is contained within the application.

As far as you trying to test the connection pooling, you should get
with a DBA and have he or she help you. Connection Pooling is there
and it works, which is a better solution, than what you're doing
currently. You should let ADO.NET, SQL Server and the O/S work for
you.

--
sp**********@ro gers.com (Do not e-mail)

[Spam Catcher]

=?Utf-8?B?QXNhZg==?= <AG**@newsgroup s.nospamwrote in
news:93******** *************** ***********@mic rosoft.com:

When using this code that suppose to use connection pooling:

TestTableAdapte r ta_Test = new TestTableAdapte r();

for (long i = 0; i < 100; i++)
{
ta_Test.Connect ion.Open();
ta_Test.Insert( i);
ta_Test.Connect ion.Close();
}

SQL Server 2005 Profiler shows "Audit Login" then insert one record
"RPC:Comple ted" and then the "Audit Logout" for each row, so there is
an Open and Close connection for each row inserted to the DB.

A connection pool is created for each unique connection string. When a
pool is created, multiple connection objects are created and added to
the pool so that the minimum pool size requirement is satisfied.
Connections are added to the pool as needed, up to the maximum pool
size.

http://msdn2.microsoft.com/en-us/lib...ca(vs.71).aspx

FYI, in the maximum pool size just happens to be 100 connections... Try
your test again with 500 - 1000 interations.
--
sp**********@ro gers.com (Do not e-mail)