AZ - 304 Microsoft Azure Architect (beta)
[Its my own notes for preparing for the exam. You are advised to verify technical correctness on your own]
This is how I am trying to find the relevant Microsoft Document for self study and preparing the exam. Already I am AZ 203 Certified developer and well versed with Azure Storage , I decided to update my skills in advanced topics on "Design Data Storage" which is part of exam's skill measured topic.
Here is the sub topic "recommend database service tier sizing".
Understanding the available database service in Azure.
- General purpose service tier
- Business critical
- Hyper scale ( Only available for Azure SQL, not for Azure SQL Managed Instance)
You must understand features of the Azure SQL , Azure SQL Managed Instance, vCore or DTU Model (purchasing model).
General Purpose service tier is the recommended (Redundancy and High Availability) on for most of the time, as it truly allows you on controlling the Compute and Storage aspects. You can scale in and scale down the storage and compute based on your usage.
The reason behind on why we need for separate storage account for Azure SQL and Azure SQL Managed Instance is , A stateless and stateful compute layer.
Stateless layer managed by Azure Service Fabric to check the health of compute node and manage the perform the failover on the Azure.
Whenever the database engine or operating system is upgraded, some part of underlying infrastructure fails, or if some critical issue is detected in the sqlservr.exe process, Azure Service Fabric will move the stateless process to another stateless compute node.
Azure SQL Managed Instance will have the separate Compute and Storage option whereas Azure SQL will have only the Service features without any specific compute or Storage.
Hyper scale Service tier features
- Supports up to 100 TB database size (Other service tier supports 1 to 4 TB)
- Rapid scale up (read only database hot standby) and scale out when the usage were lower as it relies on Compute and Storage.
- Fast database restores with in a minute rather than hours or even a day.
- Higher performance due to higher log throughput and faster commit irrespective of data volums.
Reference
https://docs.microsoft.com/en-in/azure/azure-sql/database/service-tier-general-purpose