Proper database connection disposal methods??

[Roger Twomey]

Hi

I have been disposing of my sql connections for some time (as I should) but
when I see samples I noticed that the samples don't close the connection
first. Here is what I do:

sqlconnection.open

Code

sqlconnection.close
sqlconnection.dispose()

-->>
What I see in samples looks like this:

sqlconnection.open

code

sqlconnection.dispose()

-->>

I noticed that in all the samples (where I noticed at all) that no one was
closing the connection first. Should I bother? Is one method right and the
other wrong? Are there any advantages to closing first or should I NOT close
first?

Does anyone know the answer to this?

Thanks.

[Chris R. Timmons]

"Roger Twomey" <ro******@vnet.on.ca> wrote in
news:Or**************@TK2MSFTNGP15.phx.gbl:

Hi

I have been disposing of my sql connections for some time (as I
should) but when I see samples I noticed that the samples don't
close the connection first. Here is what I do:

sqlconnection.open

Code

sqlconnection.close
sqlconnection.dispose()

-->>
What I see in samples looks like this:

sqlconnection.open

code

sqlconnection.dispose()

-->>

I noticed that in all the samples (where I noticed at all) that
no one was closing the connection first. Should I bother? Is one
method right and the other wrong? Are there any advantages to
closing first or should I NOT close first?

Does anyone know the answer to this?

Roger,

Dispose() calls Close() if the connection is still open. Use
Reflector (http://www.aisto.com/roeder/dotnet/) to examine how
SqlConnection.Dispose() operates if you're curious.

--
Hope this helps.

Chris.
-------------
C.R. Timmons Consulting, Inc.
http://www.crtimmonsinc.com/

[Roger Twomey]

Thank you.

I suspected that it did.

Do you know if there is any advantage to my closing it explicitly? Do I save
any clock cycles or is it the same either way (except of course that I have
to type more).

Thanks again!

"Chris R. Timmons" <crtimmons@X_NOSPAM_Xcrtimmonsinc.com> wrote in message
news:Xn*********************************@207.46.24 8.16...

"Roger Twomey" <ro******@vnet.on.ca> wrote in
news:Or**************@TK2MSFTNGP15.phx.gbl:

Hi

I have been disposing of my sql connections for some time (as I
should) but when I see samples I noticed that the samples don't
close the connection first. Here is what I do:

sqlconnection.open

Code

sqlconnection.close
sqlconnection.dispose()

-->>
What I see in samples looks like this:

sqlconnection.open

code

sqlconnection.dispose()

-->>

I noticed that in all the samples (where I noticed at all) that
no one was closing the connection first. Should I bother? Is one
method right and the other wrong? Are there any advantages to
closing first or should I NOT close first?

Does anyone know the answer to this?

Roger,

Dispose() calls Close() if the connection is still open. Use
Reflector (http://www.aisto.com/roeder/dotnet/) to examine how
SqlConnection.Dispose() operates if you're curious.

--
Hope this helps.

Chris.
-------------
C.R. Timmons Consulting, Inc.
http://www.crtimmonsinc.com/

[Chris R. Timmons]

"Roger Twomey" <ro******@vnet.on.ca> wrote in
news:eX**************@TK2MSFTNGP09.phx.gbl:

Thank you.

I suspected that it did.

Do you know if there is any advantage to my closing it
explicitly? Do I save any clock cycles or is it the same either
way (except of course that I have to type more).

Roger,

The performance is going to be essentially the same either way.

--
Hope this helps.

Chris.
-------------
C.R. Timmons Consulting, Inc.
http://www.crtimmonsinc.com/