To add to this, it should be noted that connection pooling is going to
keep some connections open so that the overhead of repeatedly opening and
closing connections is not incurred.
--
- Nicholas Paldino [.NET/C# MVP]
-
ni**************@exisconsulting.com
"Ignacio Machin" <ignacio.machin AT dot.state.fl.us> wrote in message
news:e3****************@tk2msftngp13.phx.gbl...
Hi,
A shot in the dark: Check that if you are using a DataReader you close it
after you finish using it., you can use this when you create it:
reader = command.ExecuteReader( CommandBehavior.CloseConnection);
after that you only have to close the DataReader
reader.Close();
and it will close the connection.
Hope this help,
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"jazzandlatin" <ja**********@yahoo.com> wrote in message
news:98**************************@posting.google.c om... Hi everybody
Could somebody tell me how it is possible to check that any connection
opened in a page be closed when the page has been published ?
My problem is that SQL server looks saturated very quickly. I 've
checked the code but something must be wrong.. there are lots of
sleeping connections in SQLServer... might this be the reason and how
can i solve the problem
Thanks a lot
Jazz
