About SQL Databse Compute redundancy

Jona 375 Reputation points

Hi every one,

I'm a little confused about two redundancy terms in SQL Database: one for compute and the other for storage

According to the price calculator:


¿what does compute redundancy mean?, ¿Is it proper for productions environment?

In the other hand ...


I think backup storage redundancy y pretty straighforward.. and ¿What about point in time restore?

I'll apprecciate any help



Azure SQL Database
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

    @Jona Thank you for reaching out.

    If my understanding is correct, you are asking the meaning of compute redundancy, point in time restore in Azure SQL Database.

    Azure SQL compute redundancy refers to the ability of Azure SQL to provide high availability and disaster recovery capabilities for your databases. It ensures that your databases remain available even in the event of a hardware or software failure. It is achieved through the use of multiple replicas of your database that are distributed across different physical locations.

    In terms of whether it is proper for a production work environment, the answer is yes. Azure SQL compute redundancy is designed to provide high availability and disaster recovery capabilities for production workloads.

    When it comes to PITR, point in time restore is a feature of Azure SQL that allows you to restore your database to a specific point in time. This is useful in situations where you need to recover your database to a specific point in time, such as when you accidentally delete data or when your database becomes corrupted.

    With point in time restore, you can restore your database to any point in time within the retention period of your backups. By default, Azure SQL retains backups for up to 7 days, but you can configure this retention period to be longer if needed.

    Azure Storage redundancy


    Restore a database from a backup in Azure SQL Database



    0 comments No comments

  2. Jona 375 Reputation points

    Thanks @Oury Ba-MSFT

    As I understand, compute redundancy also replicates the compute engine... isn't?

    In the other hand, PITR, ¿How is it configured? ¿What is "GB" supposed to be in the combobox?



  3. Jes Schultz 0 Reputation points Microsoft Employee

    Backup storage redundancy refers to where copies of your backups will be stored - locally redundant, zonally redundant, or geographically redundant. This applies to your point-in-time restore backups (the full, differential, and log backups that are used to provide you with the 1-35 days of restore capability you specify when you create or modify the database. The PITR size box in the screenshot you shared is where you will input your estimated backup storage sizes to help determine the cost of storing them.

    Backup storage redundancy also determines the redundancy of long-term retention backups, if you choose to enable those for the database. This setting is optional. (PITR is not.) https://learn.microsoft.com/en-us/azure/azure-sql/database/long-term-retention-overview?view=azuresql

    0 comments No comments