Azure SQL Database Support

  • Sitecore supports Microsoft Azure SQL Database service for the following setups:

    1. When running Sitecore XP 8.2 and later versions.
    2. When running Sitecore XP 8.1 and earlier versions and deploying to Microsoft Azure using the Sitecore Azure module.

    Sitecore does not support using Azure SQL Databases in the following situations:

    1. When using Email Experience Manager module.
    2. When running any configuration that is not mentioned in the supported list.
  • Detailed below are the known issues when using using Azure SQL Database service.

    Azure SQL version compatibility

    Sitecore supports Azure SQL Database V12.

    Transient errors (transient faults)

    The Sitecore SQL Server data provider retry mechanism is not optimal for handling transient faults when opening a connection to the Azure SQL Database. For more information about the transient errors (transient faults), please see the Microsoft Azure website.

    Upgrading older versions

    Upgrading Sitecore versions earlier than 8.2 is not supported when using Azure SQL. It may be required to temporarily switch to an on-premises Microsoft SQL Server to perform an upgrade.

    The reason is that Azure SQL Database only implements a subset of T-SQL. Even though most of the essential features of T-SQL features are available, including cursors, transactions. and triggers, some are not implemented. For more detailed information, please see the Azure SQL Database Transact-SQL differences article.

    This can make the system unable to run version upgrade scripts for Sitecore databases due to a dependency on the Global temporary tables, which are unavailable in Azure SQL Database.

    Active Geo-Replication

    Active Geo-Replication creates readable secondary databases in the same or different data center location (region). Currently, Sitecore does not support using a read-only database. If you choose to use Azure Active Geo-Replication, you must make sure that Sitecore instances (that is, Content Management, Content Delivery, Processing, and Reporting), are in the stopped state until you set the “local” Azure SQL Database as the Primary database. Alternatively, you can review experimental option to enable active secondary here: https://kb.sitecore.net/articles/610106

Applies to:

CMS 7.0+

March 30, 2016
March 30, 2017

Reference number:

422704

Keywords: 

  • Azure,
  • CMS