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:
>