Skip to content

Commit 9959992

Browse files
authored
Update SqlCommand.Execute method call description
Clarified the types of SqlCommand.Execute method calls that can trigger connection retries.
1 parent 4b5f38f commit 9959992

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

azure-sql/database/troubleshoot-common-connectivity-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@ Also, consider that the command itself requires time to execute after the connec
204204
The **ConnectRetryCount** and **ConnectRetryInterval** parameters let your **SqlConnection** object retry the connect operation without telling or bothering your program, such as returning control to your program. The retries can occur in the following situations:
205205

206206
- SqlConnection.Open method call
207-
- SqlCommand.Execute method call
207+
- SqlCommand.Execute* method calls
208208

209209
There is a subtlety. If a transient error occurs while your *query* is being executed, your **SqlConnection** object doesn't retry the connect operation. It certainly doesn't retry your query. However, **SqlConnection** very quickly checks the connection before sending your query for execution. If the quick check detects a connection problem, **SqlConnection** retries the connect operation. If the retry succeeds, your query is sent for execution.
210210

0 commit comments

Comments
 (0)