SQL Azure and Sitecore Retryer

If you are deploying Sitecore on Azure and you are using SQL Azure, you should know that you could experience some connectivity issue between your Sitecore instance and your database…

Therefore it is strongly recommended to enable a retry mechanism on Sitecore data provider to recover these intermittent connectivity issues.

This is the default configuration that you will find in your web config, and what you need to do is to switch disabled to false….

you can either keep the logging enabled/disabled to log these connectivity issues and change the interval setting, but I would recommend to keep the default value…

<retryer disabled="true" type="Sitecore.Data.DataProviders.Retryer, Sitecore.Kernel">
      <param desc="Number of tries">6</param>
      <param desc="Interval between tries">00:00:00.500</param>
      <param desc="Log each exception (should be used for debug only)">true</param>
</retryer>
Advertisements

One thought on “SQL Azure and Sitecore Retryer

  1. Enabling it is insufficient. You need to calibrate it as well. What I gathered from Microsoft:

    “The retry logic has to vary from 5 to up to 60 seconds at least. 90 could be more appropriate, if your application allows it. That way, whenever the transient faults happen you can cover a larger spectrum of waits, not just the majority of them that get resolved in 10 seconds or less, but also any outlier that goes up to 90 seconds or so. You decide what is the apprpriate time to let your customers know that the applicaton is waiting for the database to become available again.”
    – MS Premium Support

    On our end we increased the settings to 10 retries with 5 second interval. This appears to be the most stable for now.

    Liked by 2 people

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s