Before taking you through Configuring Azure Database, I would like to explain about purchasing model available in Azure to configure database.
Azure SQL Database enables you to easily purchase PaaS database engine that fits your performance and cost needs. Depending on the deployment model of Azure SQL Database, you can select the purchasing model that fits your needs. The Two purchase Model available in Azure are
- vCore-based purchasing model (recommended) that enables you to choose the exact amount of storage capacity and compute that you need for your workload.
- DTU-based purchasing model where you can choose bundled compute&storage packages balanced for common workloads.
Before Understanding DTU Based purchase model let us understand what is DTU
The DTU is Database Transaction Unit, and is a blended mix of CPU, I/O, memory (RAM), reads, and writes.
DTU-based purchasing model
The DTU-based purchasing model offers a set of preconfigured bundles of compute resources and included storage to drive different levels of application performance. Customers who prefer the simplicity of a pre-configured bundle and fixed payments each month, may find the DTU-based model more suitable for their needs. In the DTU-based purchasing model, customers can choose between Basic, Standard, and Premium service.
vCore Purchase Model:
The vCore model is based on the number of virtual CPU cores you require, and this can be scaled up as your workload increases.
The vCore-based purchasing model enables you to independently choose compute and storage resources, match on-premises performance, and optimize price. In the vCore-based purchasing model, customers pay for
- Compute (service tier + number of vCores and amount of memory + generation of hardware)
- Type and amount of data and log storage
General Purpose Business Critical and HyperScale(Preview) are the Service Tiers Supported in vCore based purchasing Model.
| Purchase Model | DTU | Vcore |
| Description | This model is based on a bundled measure of compute, storage, and IO resources. Compute sizes are expressed in terms of Database Transaction Units (DTUs) for single databases and elastic Database Transaction Units (eDTUs) for elastic pools. | This model allows you to independently choose compute and storage resources. It also allows you to use Azure Hybrid Benefit for SQL Server to gain cost savings. |
| Deployment Model Supported | Single DB and Elastic Pool | Single DB, Elastic Pool and Managed Instance |
| Service Tiers Supported | Basic, Standard and Premier | General Purpose Business Critical and HyperScale |
| Best Suited for | Best for customers who want simple, pre-configured resource options. | Best for customers who value flexibility, control, and transparency. |
You would be wondering what is Service Tiers and how they are related to Purchasing Model. Next article would throw some light on that.
CloudToon 