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
SqlConnection is for SQL Server. You need MySqlConnection – this is not part of the .NET Framework, so you will have to download it and reference it in your project. You can then create a MySqlConnection object and connect to MySQL in your application: MySqlConnection connection = new MySqlConnection(myConnString); You will also have to use … 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
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
You should either use this method: SqlCommand cmd = new SqlCommand(“dbo.workScheduleDataGrid”, sqlcon); or this method SqlCommand cmd = sqlcon.CreateCommand(); to create the command, but not both (the second assignment in your code overwrites the first one). With the second options, you need to specify the command to execute separarely: cmd.CommandText = “dbo.workScheduleDataGrid”; Also, do not … Read more