Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tjams
Starting Member
8 Posts |
 Posted - 2003-03-31 : 13:36:00
|
| I seem to be having an issue where my application is maxing out the sql server's connections. The app is an ASP.Net application and most of the data is retrieved into SQLDataReaders. When I'm done with the datareader, I close the reader and close the connection. Do I also need to destroy the connection object by setting it equal to "Nothing"? It was my understanding that this was no longer necessary with the .NET framework. Thanks for your input. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-03-31 : 13:56:59
|
| Connection pooling wil keep the connection open for a configurable period of time even after you close it.-Chad |
 |
|
|
|
|
|
Connections won't go away