This seems to be a simple question, but I wonder the disadvantages of not calling the "close()" function.
Thanks.
+9
A:
Sooner or later, you'll run into the "The Maximum Connection Limit Has Been Reached" error. I'd call that a major disadvantage.
ammoQ
2010-01-26 12:58:35
+1
A:
The connection pool will fill up and any new connections will time out waiting for a new connection from the pool.
bleeeah
2010-01-26 12:58:54
A:
a connection to the database server is open. suppose you have 100s of programs hitting the same server...
you should also dispose it
ThanosPapathanasiou
2010-01-26 12:59:42
A:
Quick simple answer is that the sooner you close, the sooner the connection can be re-used by the connection pool.
Justin Wignall
2010-01-26 12:59:56
"using using is good" is a little mantra I say to myself when conencting to sql. SqlConnection implements iDisposable so simply wrap your sql code in a "using" block to ensure your close is called automatically.
Justin Wignall
2010-01-26 13:02:25
+4
A:
Apart from exhausting the connection pool (as most answers so far have been), you are in danger of locking data.
If you are reading or writing to a table, some locking semantics will cause certain rows to be locked to other connections. This is especially true if you have any open transaction on the connection.
Reads and writes can then fail and the application will throw exceptions all over the place.
In short, always close the connection.
Oded
2010-01-26 13:02:09
Even after the sql command using the connection is done with the rows?
ThanosPapathanasiou
2010-01-26 13:04:14
A:
Each and every connection to SQL Server requires memory allocation.
So the more connections you have open the more memory that is being used and held, that could potentially be put to better use.
If you want to know just how much memory is used by connections in SQL Server, take a look at the following reference.
John Sansom
2010-01-26 13:48:51