connection pooling feature with ADO?[fixed question]

I know that ADO with SQL Server has connection pooling feature. Considering
this, I cannot understand why the problem described below occurs.
Please reply me any solution. Thanks in advance.
Regards,
Hyun-jik Bae
Environment:
SQL Server 2000
ADO 2.8
Condition:
Simultaneous one thread opens ADO connection, updates a record and closes
it. This is done 50 times per second.
Problem:
After running the condition I mentioned above for about a minute, a lot of
TCP connection to 1433 on TIME_WAIT state remains.Hi
How many connections are shown by sp_who2 during and after this period?
Regards
Mike
"Bae,Hyun-jik" wrote:

> I know that ADO with SQL Server has connection pooling feature. Considerin
g
> this, I cannot understand why the problem described below occurs.
> Please reply me any solution. Thanks in advance.
> Regards,
> Hyun-jik Bae
> --
> Environment:
> SQL Server 2000
> ADO 2.8
> Condition:
> Simultaneous one thread opens ADO connection, updates a record and closes
> it. This is done 50 times per second.
> Problem:
> After running the condition I mentioned above for about a minute, a lot of
> TCP connection to 1433 on TIME_WAIT state remains.
>
>
>|||sp_who2 says there is only one during that period. However, a lot of 1433
TCP connections still exists.
Regards,
Hyun-jik
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:D8ABCB63-D676-46B4-A152-90F084FD58BB@.microsoft.com...
> Hi
> How many connections are shown by sp_who2 during and after this period?
> Regards
> Mike
> "Bae,Hyun-jik" wrote:
>

connection pooling feature with ADO?

I know that ADO with SQL Server has connection pooling feature. Considering
this, I cannot understand why the problem described below occurs.
Please reply me any solution. Thanks in advance.
Regards,
Hyun-jik Bae
Environment:
SQL Server 2000
ADO 2.8
Condition:
Simultaneous one thread opens ADO connection, updates a record and closes
it. This is done 50 times per second.
Problem:
After running the condition I mentioned above for about a minute, every ADO
Connection object in a program occupies a TCP connection to 1433.Hi
If you are using ODBC then it might not be enabled see
http://www.aspfaq.com/show.asp?id=2155
You may also want to look at
http://msdn.microsoft.com/library/d...
ng2.asp
John
"Bae,Hyun-jik" wrote:

> I know that ADO with SQL Server has connection pooling feature. Considerin
g
> this, I cannot understand why the problem described below occurs.
> Please reply me any solution. Thanks in advance.
> Regards,
> Hyun-jik Bae
> --
> Environment:
> SQL Server 2000
> ADO 2.8
> Condition:
> Simultaneous one thread opens ADO connection, updates a record and closes
> it. This is done 50 times per second.
> Problem:
> After running the condition I mentioned above for about a minute, every AD
O
> Connection object in a program occupies a TCP connection to 1433.
>
>

Connection broken on localhost

Following error occurs when I execute stored procedure sp_updatestats to update
statistics:
...
Updating dbo.AttachmentFolderDefinition
Updating dbo.Branch
...
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead
(WrapperRead()). Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I am running the procedure from the SQL Query Analyzer locally from the server.
Sometimes the same error occurs when I do a backup or when I run other stored
procedures.
The SQL Server log and Event Log didn't help.
Any ideas ?
Thanks
Radek
Radek,
You are probably running into this issue:
FIX: General network error when you try to back up or restore a SQL
Server database on a computer that is running Windows Server 2003
http://support.microsoft.com/?id=827452
Try using TCP/IP as your network library instead of Named Pipes.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Radek Pospisil wrote:
> Following error occurs when I execute stored procedure sp_updatestats to update
> statistics:
> ...
> Updating dbo.AttachmentFolderDefinition
> Updating dbo.Branch
> ...
> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead
> (WrapperRead()). Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> I am running the procedure from the SQL Query Analyzer locally from the server.
> Sometimes the same error occurs when I do a backup or when I run other stored
> procedures.
> The SQL Server log and Event Log didn't help.
> Any ideas ?
> Thanks
> Radek
|||You are right. Thanks a lot.
Radek
Mark Allison <marka@.no.tinned.meat.mvps.org> wrote in
news:OdUmcoc4EHA.4092@.TK2MSFTNGP14.phx.gbl:

> Radek,
> You are probably running into this issue:
> FIX: General network error when you try to back up or restore a SQL
> Server database on a computer that is running Windows Server 2003
> http://support.microsoft.com/?id=827452
> Try using TCP/IP as your network library instead of Named Pipes.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>