Azure SQL: DTU vs vCore Purchasing Models Explained

The DTU model bundles compute, storage, and I/O into a single unit for simplicity, ideal for small, predictable workloads. The vCore model provides independent scaling of compute and storage, offering greater flexibility and control for complex, high-performance applications. Choosing between them depends on your need for simplicity versus granular control.

What exactly is the DTU purchasing model?

Think of Database Transaction Units (DTUs) as a 'pre-packaged meal.' Instead of picking your protein, veg, and starch separately, Microsoft bundles compute, memory, and I/O into a single measure of performance. For someone just starting with Azure or studying for the AZ-900, this is the easiest way to get a database running without getting bogged down in hardware specs.

When you select a DTU tier—like Basic, Standard, or Premium—you are essentially buying a slice of a shared resource pool. If your application has a predictable load and you don't want to spend hours tuning virtual cores or IOPS, DTUs are your best friend. It simplifies the procurement process, allowing you to scale up or down with a single slider rather than reconfiguring your entire infrastructure.

Why should you consider the vCore model instead?

While DTUs are great for simplicity, the vCore model is where the real power lies. If DTUs are a pre-packaged meal, vCore is a custom menu. It decouples compute resources from storage, meaning you can scale your CPU and RAM independently of how much data you're storing. This is a critical distinction for high-performance applications where you might have a massive dataset but only need moderate compute power, or vice versa.

Beyond just scaling, the vCore model gives you a level of transparency that DTUs lack. You can choose the specific hardware generation and the amount of memory per core. For those of you aiming for professional-grade deployments, this granularity prevents over-provisioning, which is the fastest way to blow through your Azure budget. It's about having the right tool for the specific job rather than a one-size-fits-all approach.

When is DTU the right choice for your project?

You should stick with the DTU model if you're managing small, predictable applications or development environments. For example, if you're building a simple internal company directory or a low-traffic blog, the administrative overhead of managing vCores is simply not worth it. DTUs allow you to get your environment live in minutes without needing a deep background in database administration.

In the context of the AZ-900 exam, remember that DTUs are designed for 'simplicity.' If a scenario describes a user who wants a quick setup with minimal configuration and a predictable monthly cost, DTU is almost always the correct answer. It removes the guesswork, making it the go-to choice for entry-level projects and students who are just dipping their toes into the Azure ecosystem.

How does vCore mapping work in the real world?

In the vCore model, you aren't guessing based on a 'unit'—you're dealing with actual virtualized hardware. You'll encounter different service tiers, such as General Purpose, Business Critical, and Hyperscale. For instance, the General Purpose tier is balanced for most workloads, while Business Critical is designed for apps that require low latency and high availability, often utilizing local SSDs for faster I/O.

Mapping these resources means you can specifically allocate, for example, 2 vCores with 5.1 GB of RAM per core. This allows you to align your Azure spend directly with your application's performance metrics. If you notice your CPU usage is hitting 90% but your storage is only 10% full, you can simply add more vCores without paying for unnecessary storage upgrades. This level of precision is what separates a junior admin from a seasoned Azure architect.

Which model is more cost-effective for scaling?

Cost-effectiveness depends entirely on your scale. For tiny apps, DTUs are often cheaper and more straightforward. However, as you grow, the vCore model becomes the financial winner due to the Azure Hybrid Benefit. If your organization already owns SQL Server licenses on-premises, you can apply them to vCore nodes, drastically reducing your hourly rate—a feature not available in the DTU model.

Additionally, the vCore model supports 'Serverless' compute. This is a game-changer for workloads that are intermittent. Instead of paying for a database to sit idle, Serverless automatically scales compute based on demand and pauses the database during periods of inactivity. You only pay for the seconds you actually use. When you compare that to the fixed cost of a DTU tier, the savings for sporadic workloads can be massive.

How do you master these concepts for the AZ-900 exam?

Understanding the difference between DTU and vCore is a staple of the Azure Fundamentals exam, but reading a blog post is only the first step. To truly lock this in, you need to see how Microsoft phrases these questions. They love to give you a scenario—like a company needing 'maximum flexibility' or 'minimal management'—and ask you to pick the model.

That's why we built our practice platform. At Cert Sensei, we provide 1,000 expert-curated Microsoft Azure Fundamentals (AZ-900) practice questions. We don't just tell you if you're wrong; we provide detailed expert reasoning for every answer so you understand the 'why' behind the 'what.' Plus, our domain-level analytics will show you exactly where you're struggling—whether it's in cloud concepts or specific services like Azure SQL—so you can stop wasting time on what you already know and focus on your weak points.

❓ Frequently Asked Questions