You need to design a highly available Azure SQL database that meets the following requirements:
✑ Failover between replicas of the database must occur without any data loss.
✑ The database must remain available in the event of a zone outage.
✑ Costs must be minimized.
Which deployment option should you use?
To meet the requirement of failover between replicas without data loss and remain available during a zone outage, Azure SQL Database Business Critical is the best option. This tier ensures high availability and fault tolerance by providing zone redundancy and multiple readable replicas. Although it is a more expensive option, it guarantees no data loss and fulfills the requirement of maintaining availability during zone outages. Neither the Basic nor Standard tiers meet the zone redundancy requirement, and while the Serverless option might offer cost savings, it does not guarantee data loss prevention in failover scenarios or the required availability during zone outages.
Where are you mlantonis
Its BC for sure
Both AZ sql database standard and serverless(both are general purpose) support zone redundancy. It's hard to compare cost between AZ database standard and AZ database serverless without a usage patterns. In general, we can say Az database serverless is cost-effective. So the given answer might be correct.
"Auto-failover groups support geo-replication of all databases in the group to only one secondary server in a different region" ,So ,if you need only one secondary server to support failover, you must use Geo-Redundancy. not Zone Redundancy. If you want in same regions ,you need more servers,which is not min cost https://learn.microsoft.com/en-us/azure/azure-sql/database/auto-failover-group-sql-db?view=azuresql&tabs=azure-powershell
Azure SQL DB Standard tier only supports LRS. https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell#basic-standard-and-general-purpose-service-tier-locally-redundant-availability
While Azure SQL Database Serverless does offer cost savings, it may not meet your specific requirements for a few reasons: Data Loss: Azure SQL Database Serverless does not guarantee that committed data is never lost due to failures. This could potentially lead to data loss during failover, which does not align with your requirement for failover between replicas of the database to occur without any data loss. Availability during Zone Outages: While Azure SQL Database Serverless does provide automatic scaling and pausing/resuming of databases, it does not specifically guarantee availability in the event of a zone outage1.
Azure Database Serverless. This question appears a lot of time, with differents options as answer. Always the answers are (in this order): 1. Azure SQL Database Premium 2. Azure SQL Database Serverless 3. Azure SQL Database Business Critical If there is only one of them, select it. If there are 2 of them, remember the order, and select the option in the order showed here
Should the order be 1. Azure SQL Database Serverless 2. Azure SQL Database Premium 3. Azure SQL Database Business Critical as SQL Database Serverless is part of general purpose, presumably cheaper than SQL Database Premium ?
Premium -> Serverless -> BC, that's the preferred order.
Answers by order. 1. Azure SQL Database Premium 2. Azure SQL Database Serverless 3. Azure SQL Database Business Critical
Zone-redundant configuration for the General Purpose service tier is offered for both serverless and provisioned compute for databases in vCore purchasing model. Serverless is assumed to be cheaper https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell
Agree. Go here with Serverless option. Reference: https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview?view=azuresql&tabs=general-purpose#regions-supporting-80-maximum-vcores-with-availability-zones-for-general-purpose
Agree. I checked in Azure Price Calculator. It seems event obvious to be cheaper by serveless as it requires less resources to be engaged
Zone-redundant availability is available to databases in the General Purpose, Premium, Business Critical and Hyperscale service tiers of the vCore purchasing model, and not the Basic and Standard service tiers of the DTU-based purchasing model. Zone-redundant availability ensures Recovery Point Objective (RPO) which indicates the amount of data loss is zero. Taken from: https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell#:~:text=ensures%20Recovery%20Point%20Objective%20(RPO)%20which%20indicates%20the%20amount-,of%20data%20loss,-is%20zero.
Zone-Redundand is available in General Purpose Serverless. General Purpose is in Locally redundant availability model. Locally redundant availability is available to all databases in all service tiers and Recovery Point Objective (RPO) which indicates the amount of data loss is zero. So you are wrong.
It's a bit old question, because now, both Serverless y Business Premium are valid, so i think that is a little better AZure Serverless
To design a highly available Azure SQL database that meets the requirements of failover without data loss, availability during zone outages, and cost minimization, you should choose option B: Azure SQL Database Business Critical. Azure SQL Database Business Critical is designed for high availability and fault tolerance. It provides an SLA that ensures failover without data loss and remains available even in the event of a zone outage. This service tier is specifically designed for mission-critical workloads and offers replication of data across multiple availability zones. Options A (Azure SQL Database Serverless), C (Azure SQL Database Basic), and D (Azure SQL Database Standard) do not offer the same level of high availability, failover guarantees, and zone-resilience as Azure SQL Database Business Critical. Therefore, option B is the best choice for meeting the given requirements.
To meet the requirements of high availability, failover without data loss, and availability in the event of a zone outage, you should choose the Azure SQL Database Business Critical deployment option. So, the correct answer is: B. Azure SQL Database Business Critical
Business Critical tier is typically more expensive compared to the Serverless tier as Business Critical tier offers higher availability, faster recovery from failures, and guarantees a shorter RPO and RTO(5 and 30sec).
B is Honey availability = Three replicas, one read-scale replica, zone-redundant high availability (HA)
Azure SQL Database Business Critical is cheaper.
its either A or B also serverless is a compute tier not performance tier both general purpose or hyperscale supports surverless deployments.
The best option for your requirements would be **B. Azure SQL Database Business Critical**. This tier supports local redundancy within an Azure region and provides the highest resilience to failures, with multiple readable replicas, and failover with no data loss. It's designed for applications that require low-latency responses and high transaction rates, and it also provides the highest level of business continuity capabilities, which aligns with your requirement for the database to remain available in the event of a zone outage. However, it's important to note that while the Business Critical tier provides the highest level of performance and availability, it also comes with higher costs compared to other tiers. Therefore, it's crucial to balance your specific needs and budget when making a decision.
Azure SQL Database Business Critical is the only service tier that meets all the requirements. It provides high availability and performance by using local SSD storage and a cluster of database replicas. It supports zone redundancy, which means that the replicas are distributed across different availability zones within the same region. It also supports automatic failover with zero data loss guarantee. However, it is also the most expensive service tier among the options. Azure SQL Database Serverless does not meet the requirement of zero data loss failover, as it uses the General Purpose service tier under the hood. It also does not support zone redundancy. It is a cost-effective option for intermittent and unpredictable workloads, as it scales compute resources based on usage and pauses the database when inactive.
Azure SQL Database Serverless meets the requirements of zero data loss failover as all service tiers work in locally redundant availability. Locally redundant availability is available to all databases in all service tiers and Recovery Point Objective (RPO) which indicates the amount of data loss is zero. https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell
A is correct