SqlDataReader in ASP.NET deallocation and close

Question

Does the following code, cleanup all SqlDataReaders correctly:

using (IDataReader reader = SqlHelper.GetDataReader(sql.ToString())) {
    if (reader.Read()) {
        result = reader.IsDBNull(0) ? string.Empty : reader[0].ToString();
    }
}

I have some concurrency/deallocation issues in my code and trying to hunt them down.

where do you capture the concurrency/deallocation issue, is there any stack strace ? — Turbot
– Turbot, Commented May 23, 2012 at 2:27

mgnoonan · Accepted Answer · 2012-05-23 02:25:07Z

2

Dispose() will be called on the IDataReader automatically, once the end of the using statement goes out of scope. Also make sure that the reader is created with the CommandBehavior.CloseConnection so that the reader will dispose of the connection once it is disposed.

But I don't see any other code involving the connection. If you are using the classic SqlHelper class, that maybe the source of the issue...

answered May 23, 2012 at 2:25

mgnoonan

7,2005 gold badges26 silver badges28 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

SqlDataReader in ASP.NET deallocation and close

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related