1

Microsoft state, "If the SqlConnection goes out of scope, it won't be closed". I don't understand this at all. SqlConnection is an ADO.NET managed object, even if it using an unmanaged resource behind the scenes, so why is the Garbage Collector not cleaning it up? When it goes out of scope it should be destroyed. Can someone please shed some light on this, it's breaking my brain.

https://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.close%28v=vs.110%29.aspx

Thanks

mils
  • 1,878
  • 2
  • 21
  • 42
  • 2
    Maybe check out [will SqlConnection get disposed for GC](http://stackoverflow.com/questions/3637549/will-sqlconnection-get-disposed-by-gc) for a good general discussion of this issue. At the end of the day though, you shouldn't expect too much help because if you're letting an open connection fall out of scope, it's a bug in your code, plain and simple. – Damien_The_Unbeliever Feb 25 '15 at 08:28

1 Answers1

2

SqlConnection is disposed when it is finalized. This happens because it inherits from Component, which has a finalizer that calls Dispose. Finalization is one of the steps in garbage collection. Garbage collection runs non-deterministically, i.e. whenever the CLR feels like it. Garbage collection in C# is totally unrelated to an object going out of scope.

So if a SqlConnection goes out of scope, it will at some point in the future be finalized and therefore closed. This is bad because until that finalization hapens, you are wasting resources. Later in your program you might fail to open a connection because too many connections are already open (even though they are not actually in use and just waiting to be finalized).

This is why it is strongly recommended that you Dispose your SqlConnections after you have finished using them.

(Don't read this as a canonical truth of how SqlConnection finalization works. I simplified the details in order to focus on the difference between finalization and explicit disposal).

Community
  • 1
  • 1
Jared Moore
  • 3,765
  • 26
  • 31