如果没有调用SqlConnection.Close（）或SqlConnection.Dispose（），它会是什么？

Question

I just found that one ASP.NET web application in my company would connect to a SQL Server 2008 R2 database to read/write data, but in some part of codes, both SqlConnection.Close() and SqlConnection.Dispose() are never called after using the connection.

From MSDN, SqlConnection Class :

If the SqlConnection goes out of scope, it won't be closed. Therefore, you must explicitly close the connection by calling Close or Dispose.

I use sp_who and find that more and more connections are created as I perform some database access via the web application. But after a few minutes, some connections seems dropped.

Is there anything .Net runtime done to handle such case that SqlConnection.Close() and SqlConnection.Dispose() are not called? And is there any potential problems which affect the performance and stability?

Answer 1

It will go OK and you won't get any error for some time. As your application runs and each time you open a SQL connection and keep it non closed, after sometime you SQL connection pool will got full and system throws connection pool overflow error as you try to open a new SQL connection.

So always keep a connection close code within your function.