This article provides information about the support for various database-level SQL Server scaling, high-availability and failover features.
The information is intentionally simplified to provide a general overview of compatibility. For additional details about the technologies that are outlined, refer to documentation from Microsoft.
Support by Sitecore | Standby category | Automatic failover | Readable secondaries | Writable secondaries | |
Replication | |||||
Snapshot Replication | – | cold | – | – | – |
Transactional Replication | Sitecore XP 9.0.0 and higher, Experimental for CMS 6.0– XP 8.2.7 [4] |
warm | – | ✓ | – |
Peer-to-Peer Replication | – | warm | – | – | – |
Merge Replication | – [5] | warm | – | – | – |
Azure Geo-Replication | Experimental [4] | warm | ✓ | ✓ | – |
High-availability | |||||
Log Shipping | – | warm | – | – | – |
Database Mirroring [2] | Sitecore CMS 6.6—8.1 |
warm, hot | ✓ | – | – |
AlwaysOn Availability Groups [3] | Sitecore XP 8.2 and higher | warm, hot | ✓ | – | – |
For the purpose of this article, the following definitions are used:
High-availability categories
Defines the risk of data loss and expected recovery time when using the corresponding technology.
Cold Standby | Warm Standby | Hot Standby | |
Data Loss | Likely | Possible | No |
Recovery Time | Hours | Minutes/Hours | Minutes |
Automatic failover
Defines whether the setup allows Sitecore instances to automatically switch to failover/secondary SQL Database instance in case of an outage.
Readable secondaries
Defines whether the setup allows Sitecore instances to read data from secondary SQL databases, effectively enabling a content delivery scenario.
Writable secondaries
Defines whether the setup allows Sitecore instances to write data to secondary SQL databases, effectively enabling a content editing scenario.