Upravit

Sdílet prostřednictvím

Configurable retry logic configuration file with SqlClient

  • Článek

Applies to: .NET Framework .NET .NET Standard

Download ADO.NET

The default retry method when the safety switch is enabled is the SqlConfigurableRetryFactory.CreateNoneRetryProvider for both SqlConnection and SqlCommand. You can specify a different retry method by using a configuration file.

Configuration sections

Default retry logic options for an application can be changed by adding the following sections inside the configSections section of the configuration file:

  • SqlConfigurableRetryLogicConnection: to specify the default retry logic for SqlConnection.
<section name="SqlConfigurableRetryLogicConnection"
        type="Microsoft.Data.SqlClient.SqlConfigurableRetryConnectionSection, Microsoft.Data.SqlClient"/>
  • SqlConfigurableRetryLogicCommand: to specify the default retry logic for SqlCommand.
<section name="SqlConfigurableRetryLogicCommand"
        type="Microsoft.Data.SqlClient.SqlConfigurableRetryCommandSection, Microsoft.Data.SqlClient"/>
  • AppContextSwitchOverrides: .NET Framework supports AppContext switches via an AppContextSwitchOverrides section, which doesn't need to be defined explicitly. To turn on a switch in .NET Core, you must specify this section.
<section name="AppContextSwitchOverrides"
        type="Microsoft.Data.SqlClient.AppContextSwitchOverridesSection, Microsoft.Data.SqlClient"/>

Note

The following configurations should be specified inside the configuration section. Declare these new sections to configure the default retry logic through an application configuration file.

Enable safety switch

Note

Starting from Microsoft.Data.SqlClient v4.0, the App Context switch "Switch.Microsoft.Data.SqlClient.EnableRetryLogic" will no longer be required to use the configurable retry logic feature. The feature is now supported in production. The default behavior of the feature will continue to be a non-retry policy, which will need to be overridden by client applications to enable retries.

You can enable the safety switch through a configuration file. To learn how to enable it through application code, see Enable configurable retry logic.

<runtime>
    <AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableRetryLogic=true"/>
</runtime>
  • .NET Core: supports multiple, semi-colon (;) delimited switches like .NET Framework.
<AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableRetryLogic=true"/>

Connection section

The following attributes can be used to specify the default retry logic for all SqlConnection instances in an application:

  • numberOfTries: sets the number of times to try.

  • deltaTime: sets the gap time interval as a TimeSpan object.

  • minTime: sets the allowed minimum gap time interval as a TimeSpan object.

  • maxTime: sets the allowed maximum gap time interval as a TimeSpan object.

  • transientErrors: sets the list of transient error numbers on which to retry.

  • retryMethod: specifies a retry method creator that receives the retry configuration via a SqlRetryLogicOption parameter and returns a SqlRetryLogicBaseProvider object.

  • retryLogicType: sets a custom retry logic provider, which contains the retry method creators that provide the retryMethod. These methods should meet the criteria for retryMethod. The fully qualified type name of the provider should be used. For more information, see Specifying fully qualified type names.

Note

It's not required to specify the retryLogicType if you use the built-in retry providers. To find the built-in retry providers, see Internal retry logic providers in SqlClient.

Command section

The following attribute can also be set for all SqlCommand instances in an application:

  • authorizedSqlCondition: Sets a pre-retry regular expression for SqlCommand.CommandText to filter specific SQL statements.

Note

The regular expression is case sensitive.

Examples

  • Attempts to establish a connection up to three times with an approximate 1-second delay between tries by using the SqlConfigurableRetryFactory.CreateFixedRetryProvider method and the default transient error list:

    <SqlConfigurableRetryLogicConnection retryMethod ="CreateFixedRetryProvider" 
                                        numberOfTries ="3" deltaTime ="00:00:01"/>

  • Attempts to establish a connection up to five times with up to a 45-second delay between tries by using the SqlConfigurableRetryFactory.CreateExponentialRetryProvider method and the default transient error list:

    <SqlConfigurableRetryLogicConnection retryMethod ="CreateExponentialRetryProvider" 
                    numberOfTries ="5" deltaTime ="00:00:03" maxTime ="00:00:45"/>

  • Attempts to execute a command up to four times with a delay between 2 and 30 seconds by using the SqlConfigurableRetryFactory.CreateIncrementalRetryProvider method and the default transient error list:

    <SqlConfigurableRetryLogicCommand retryMethod ="CreateIncrementalRetryProvider"
                    numberOfTries ="4" deltaTime ="00:00:02" maxTime ="00:00:30"/>

  • Attempts to execute a command up to eight times with a delay from one second to one minute. It's limited to commands with CommandText containing the word SELECT and exception numbers 102 or 997. It uses the built-in SqlConfigurableRetryFactory.CreateIncrementalRetryProvider method:

    <SqlConfigurableRetryLogicCommand retryMethod ="CreateIncrementalRetryProvider" 
                        numberOfTries ="8" deltaTime ="00:00:01" maxTime ="00:01:00"
                        transientErrors="102, 997"
                        authorizedSqlCondition="\b(SELECT)\b"/>

Note

In the next two samples, you can find the custom retry logic source code from Configurable retry logic core APIs in SqlClient. It's assumed the CreateCustomProvider method is defined in the CustomCRL_Doc.CustomRetry class in the CustomCRL_Doc.dll assembly that is in the application's executing directory.

  • Attempts to establish a connection up to five times, with a delay between 3 and 45 seconds, error numbers 4060, 997, and 233 in the list, and using the specified custom retry provider:

    <SqlConfigurableRetryLogicConnection retryLogicType ="CustomCRL_Doc.CustomRetry, CustomCRL_Doc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"
                    retryMethod ="CreateCustomProvider" 
                    numberOfTries ="5" deltaTime ="00:00:03" maxTime ="00:00:45"
                    transientErrors ="4060, 997, 233"/>

  • This sample behaves like the previous one:

    <SqlConfigurableRetryLogicConnection retryLogicType ="CustomCRL_Doc.CustomRetry, CustomCRL_Doc"
                    retryMethod ="CreateCustomProvider" 
                    numberOfTries ="5" deltaTime ="00:00:03" maxTime ="00:00:45"
                    transientErrors ="4060, 997, 233"/>

Note

Retry logic providers will be cached at the first use on a connection or command for future use during an application's lifetime.

Note

Any errors when reading an application configuration file for retry logic settings won't cause errors in the application. The default SqlConfigurableRetryFactory.CreateNoneRetryProvider will be used instead.

You can use event source tracing to verify or troubleshoot issues with configuring retry logic. For more information, see Enable event tracing in SqlClient.

See also