DTU vs vCore pricing models in Azure - Visual Side-by-Side Comparison

Process Flow - DTU vs vCore pricing models

Start: Choose Pricing Model

↓

DTU Model

↓

Fixed Bundle of Resources

↓

Pay for Combined CPU, Memory, IO

↓

Simple, Less Flexible

↓

vCore Model

↓

Choose CPU Cores & Memory

↓

Pay Separately for Compute & Storage

↓

More Transparent & Flexible

You start by choosing between DTU or vCore pricing. DTU bundles resources together for simple pricing. vCore lets you pick CPU and memory separately for more control.

Execution Sample

Azure

Choose pricing model: DTU or vCore
If DTU:
  Pay fixed bundle
Else if vCore:
  Select cores and memory
  Pay separately for compute and storage

This flow shows how you pick a pricing model and pay based on resource bundles or separate components.

Process Table

Step	Action	Choice/Value	Effect	Notes
1	Choose pricing model	DTU	Pay fixed bundle of CPU, memory, IO	Simple pricing, less flexible
2	Calculate cost	DTU level 100	Fixed monthly price	Includes all resources combined
3	Choose pricing model	vCore	Select CPU cores and memory	More control over resources
4	Calculate compute cost	4 vCores	Pay per core per hour	Separate from storage
5	Calculate storage cost	500 GB	Pay per GB per month	Storage billed separately
6	Total cost	Compute + Storage	Sum of separate charges	Transparent billing
7	End	-	-	Pricing decision complete

💡 Pricing model chosen and cost calculated based on selected resources

Status Tracker

Variable	Start	After DTU Choice	After vCore Choice	Final
PricingModel	None	DTU	vCore	vCore
CPU	N/A	Included in DTU	4 cores selected	4 cores
Memory	N/A	Included in DTU	16 GB selected	16 GB
Storage	N/A	Included in DTU	500 GB selected	500 GB
Cost	0	Fixed bundle price	Sum of compute + storage	Sum of compute + storage

Key Moments - 3 Insights

Why does DTU pricing feel simpler but less flexible?

DTU bundles CPU, memory, and IO together into one fixed price (see execution_table step 2), so you pay for a combined resource package without choosing individual parts.

How does vCore pricing give more control over resources?

With vCore, you pick CPU cores and memory separately (execution_table step 3), and pay for compute and storage independently, allowing you to tailor resources to your needs.

Why is storage cost separate in vCore but included in DTU?

DTU pricing includes storage in the fixed bundle (step 2), while vCore charges storage separately (step 5) to give transparent billing and flexibility.

Visual Quiz - 3 Questions

Look at the execution_table, what is the pricing model chosen at step 3?

A DTU

B Both DTU and vCore

C vCore

D None

💡 Hint

Check the 'Choice/Value' column at step 3 in execution_table

At which step does the cost calculation for storage happen in vCore pricing?

A Step 5

B Step 4

C Step 2

D Step 6

💡 Hint

Look for 'Calculate storage cost' in the 'Action' column of execution_table

If you increase CPU cores in vCore pricing, which variable in variable_tracker changes?

A PricingModel

B CPU

C Storage

D Cost

💡 Hint

Check the 'CPU' row in variable_tracker to see how CPU cores change

Concept Snapshot

DTU pricing bundles CPU, memory, and IO into one fixed package.
vCore pricing separates compute (CPU cores, memory) and storage.
DTU is simpler but less flexible.
vCore offers transparent, customizable billing.
Choose DTU for ease, vCore for control and scalability.

Full Transcript

This visual execution compares DTU and vCore pricing models in Azure SQL. You start by choosing a pricing model. DTU bundles CPU, memory, and IO into a fixed price, making it simple but less flexible. vCore lets you pick CPU cores and memory separately and pay for compute and storage independently, offering more control and transparency. The execution table shows steps choosing models, calculating costs, and final pricing. Variable tracking shows how CPU, memory, storage, and cost values change depending on the model. Key moments clarify why DTU is simpler and vCore more flexible. The quiz tests understanding of steps and variable changes. The snapshot summarizes key differences and when to choose each model.