1 min read
The built-in active geo-replication has been generally available to the Premium databases for over a year. As a growing number of SaaS customers use the multi-tenant design pattern, including the use of elastic pools, we receive feedback that consistent geo-replication capability independent of the database type would be beneficial to these applications. Today we are happy to announce that we have extended active geo-replication to all service tiers. The capabilities now available to all databases include:
- Ability to create the secondary database in any region in the world
- Ability to connect to the secondary database with read-only access
- Ability to create up to 4 parallel secondary databases in the same or different region
- Ability to configure performance objective of the secondary database
- When failover is activated to one of the secondary databases, other secondaries are automatically linked to the new primary
The secondary database is priced at 1x price of the selected performance objective. For example if your application requires a P2 primary database but the secondary databases is configured with P1 performance objective you will be charged the price of P1 for the secondary. This option is not recommended for applications with high database write activity as it may result in increased replication lag and therefore, has high risk of substantial data loss after failover. Note, the secondary database must be in the same service tier than the primary. Therefore if you are using S0 or P1 performance objective for the primary you cannot configure a secondary database with lower performance objective.
To take advantage of this additional functionality you can create one or several readable secondaries of any Basic or Standard database on V12 server as illustrated below. You will not be required to upgrade to Premium.
Deprecation of Standard geo-replication
Because active geo-replication is a superset of standard geo-replication and is available to all service tiers, the standard geo-replication configuration option will be retired in 12 months. Until then the feature will remain fully supported.