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.

Practice

1. What does the DTU pricing model in Azure SQL Database combine into a single unit?

easy

A. Only memory resources

B. Only CPU resources

C. Storage and network bandwidth

D. CPU, memory, and I/O resources bundled together

Solution

1. Step 1: Understand DTU components

   DTU stands for Database Transaction Unit, which bundles CPU, memory, and I/O into one unit for simple pricing.

2. Step 2: Compare options to DTU definition

   Only CPU, memory, and I/O resources bundled together correctly lists CPU, memory, and I/O bundled together.

3. Final Answer:

   CPU, memory, and I/O resources bundled together -> Option D

4. Quick Check:

   DTU = bundled CPU, memory, I/O [OK]

Hint: DTU bundles CPU, memory, and I/O as one unit [OK]

Common Mistakes:

• Thinking DTU is only CPU or memory
• Confusing DTU with storage pricing
• Assuming DTU separates resources

2. Which of the following is the correct way to describe the vCore pricing model?

easy

A. It lets you select CPU and memory separately

B. It bundles CPU, memory, and I/O into one unit

C. It charges only for storage used

D. It is only available for on-premises databases

Solution

1. Step 1: Recall vCore pricing features

   The vCore model allows choosing CPU and memory independently for more control over resources.

2. Step 2: Match options to vCore traits

   It lets you select CPU and memory separately correctly states that CPU and memory are selected separately, unlike DTU.

3. Final Answer:

   It lets you select CPU and memory separately -> Option A

4. Quick Check:

   vCore = separate CPU and memory selection [OK]

Hint: vCore separates CPU and memory choices [OK]

Common Mistakes:

• Confusing vCore with DTU bundling
• Thinking vCore charges only storage
• Assuming vCore is for on-premises only

3. If a workload requires high CPU but moderate memory, which pricing model is better to optimize cost?

medium

A. vCore model because you can choose more CPU and less memory

B. DTU model because it bundles all resources

C. DTU model because it charges separately for CPU

D. vCore model because it bundles CPU and memory

Solution

1. Step 1: Analyze workload needs

   The workload needs high CPU but only moderate memory, so flexibility in resource selection is important.

2. Step 2: Compare pricing models for flexibility

   DTU bundles CPU and memory, so you cannot adjust them separately. vCore lets you pick CPU and memory independently, optimizing cost.

3. Final Answer:

   vCore model because you can choose more CPU and less memory -> Option A

4. Quick Check:

   High CPU + moderate memory = vCore better [OK]

Hint: Choose vCore for flexible CPU and memory [OK]

Common Mistakes:

• Choosing DTU for flexible resource needs
• Thinking DTU charges CPU separately
• Confusing bundling in vCore

4. A user selects the DTU pricing model but wants to increase only memory without changing CPU. What is the issue?

medium

A. DTU allows only CPU scaling, not memory

B. DTU does not allow separate scaling of CPU and memory

C. DTU charges extra for memory upgrades only

D. DTU automatically scales memory without user input

Solution

1. Step 1: Understand DTU scaling limits

   DTU bundles CPU, memory, and I/O, so you cannot scale memory independently without affecting CPU.

2. Step 2: Identify the problem with user's request

   The user wants to increase only memory, which DTU does not support because of bundled resources.

3. Final Answer:

   DTU does not allow separate scaling of CPU and memory -> Option B

4. Quick Check:

   DTU = no separate CPU/memory scaling [OK]

Hint: DTU bundles resources; no separate scaling [OK]

Common Mistakes:

• Thinking DTU allows memory-only scaling
• Assuming DTU charges extra for memory only
• Believing DTU auto-scales memory

5. A company has a workload with unpredictable spikes in CPU and memory usage. They want to minimize cost but maintain performance. Which pricing model and strategy should they choose?

hard

A. Use DTU model with a high DTU level to cover spikes

B. Use vCore model but fix CPU and memory to lowest levels

C. Use vCore model with autoscaling to adjust CPU and memory dynamically

D. Use DTU model and manually upgrade when spikes occur

Solution

1. Step 1: Analyze workload characteristics

   The workload has unpredictable spikes in CPU and memory, requiring flexible resource adjustment to maintain performance.

2. Step 2: Evaluate pricing models and strategies

   DTU bundles resources and requires fixed levels, so it is less flexible and may lead to overpaying. vCore supports autoscaling, allowing dynamic adjustment of CPU and memory to match demand and minimize cost.

3. Step 3: Choose best option

   Use vCore model with autoscaling to adjust CPU and memory dynamically uses vCore with autoscaling, which fits the need for flexibility and cost control.

4. Final Answer:

   Use vCore model with autoscaling to adjust CPU and memory dynamically -> Option C

5. Quick Check:

   Unpredictable spikes = vCore + autoscaling [OK]

Hint: Autoscale CPU and memory with vCore for spikes [OK]

Common Mistakes:

• Choosing fixed DTU for variable workloads
• Manually upgrading DTU causing delays
• Fixing vCore resources too low