S
sljones
Hi There,
I am using the SQLHelper class and have implemented runsp,
executescalar, executedataset, and executereader.
I am using connection pooling between IIS and SQL Server.
All these clases except for ExecuteReader are re-using connections
properly,
ExecuteReader for some reason keeps creating new connections as it is
not closing the previous one properly.
Any ideas?
I do issue a datareader.close command. But as I am using SQLHelper in
a data layer, I am passing the datareader back to the business layer
but I can't close the connection at this point as I wont be able to
use my reader. Is the reader.close suppose to close the connection or
just the reader? How can I close the connection outside the data
layer.
Any help much appreciated.
I am using the SQLHelper class and have implemented runsp,
executescalar, executedataset, and executereader.
I am using connection pooling between IIS and SQL Server.
All these clases except for ExecuteReader are re-using connections
properly,
ExecuteReader for some reason keeps creating new connections as it is
not closing the previous one properly.
Any ideas?
I do issue a datareader.close command. But as I am using SQLHelper in
a data layer, I am passing the datareader back to the business layer
but I can't close the connection at this point as I wont be able to
use my reader. Is the reader.close suppose to close the connection or
just the reader? How can I close the connection outside the data
layer.
Any help much appreciated.