Can SqlConfigurableRetryProviders be re-used

[Vandersteen]

Is it advised to always create a new retry provider for every connection / command or can they be re-used across many connections / commands. It is unclear from the documentation what the best practices are:

private static readonly SqlRetryLogicBaseProvider DefaultRetryProvider = SqlConfigurableRetryFactory.CreateIncrementalRetryProvider(
                new SqlRetryLogicOption()
                {
                    NumberOfTries = 5,
                    MaxTimeInterval = TimeSpan.FromSeconds(10)
                }
            );
            
//...

public IConnection GetConnection()
{
    var connection = new SqlConnection(_options.ConnectionString);
    connection.RetryLogicProvider = DefaultRetryProvider;
    return connection;
}

vs creating it for every connection

public IConnection GetConnection()
{
    var connection = new SqlConnection(_options.ConnectionString);
    connection.RetryLogicProvider = SqlConfigurableRetryFactory.CreateIncrementalRetryProvider(...);
    return connection;
}

Same thing goes for commands

[arellegue]

You may find the information at https://devblogs.microsoft.com/azure-sql/configurable-retry-logic-for-microsoft-data-sqlclient/ to have all the answers to your queries.

[DavoudEshtehari]

If you have a similar retry logic with all the objects, it's safe re-using a provider, which is exposed in SqlConfigurableRetryFactory. The way you should create a new provider and consume it, depends on your application, like concurrent calls and maintenance policy.

I'll convert this issue to a discussion.