Yes. CommandTimeout is how long a single command can take to complete. ConnectionTimeout is how long it can take to establish a connection to the server to start with. For instance, you may be executing relatively long-running queries – it’s perfectly okay for them to take 10 minutes to complete, but if it took 10 … Read more
You should be using SqlConnection.State e.g, using System.Data; if (myConnection != null && myConnection.State == ConnectionState.Closed) { // do something // … }
Since you have a using block, the Dispose method of the SQLCommand will be called and it will close the connection: // System.Data.SqlClient.SqlConnection.Dispose disassemble protected override void Dispose(bool disposing) { if (disposing) { this._userConnectionOptions = null; this._poolGroup = null; this.Close(); } this.DisposeMe(disposing); base.Dispose(disposing); }
Stick to option a. The connection pooling is your friend.
Yes Yes. Either way, when the using block is exited (either by successful completion or by error) it is closed. Although I think it would be better to organize like this because it’s a lot easier to see what is going to happen, even for the new maintenance programmer who will support it later: using … Read more
I’ve done some tests since asking this question and found most if not all answers on my own, since no one else replied. Please let me know if I’ve missed anything. Q1: Is connection automatically enlisted in transaction? Yes, unless enlist=false is specified in the connection string. The connection pool finds a usable connection. A … Read more