C
Clement
Hi,
i had develope asp.net using the webservice as the input point for
processing. in the webservice, i had use the threading process the request.
this is very data intensive process using sql server 2000 standard edition
in the production server with .Net framework 1.0 SP2.
i notice that when i run the test in production, the sqlconnection doesn't
close even though i do have the sqlconnection.close in every statement i
have in the Try...catch...finally block. but if i run in my development
server, i can see sqlconnection is close every time after the sql statement
.. anyone out there have any idea ?
Note: i use the sql profiler to monitor the sql activity in the same
database with is calling by development server and production server.
development server have dotnet framework 1.0 SP2 and 1.1 installed.
i had develope asp.net using the webservice as the input point for
processing. in the webservice, i had use the threading process the request.
this is very data intensive process using sql server 2000 standard edition
in the production server with .Net framework 1.0 SP2.
i notice that when i run the test in production, the sqlconnection doesn't
close even though i do have the sqlconnection.close in every statement i
have in the Try...catch...finally block. but if i run in my development
server, i can see sqlconnection is close every time after the sql statement
.. anyone out there have any idea ?
Note: i use the sql profiler to monitor the sql activity in the same
database with is calling by development server and production server.
development server have dotnet framework 1.0 SP2 and 1.1 installed.