Azure SQL Managed Instance Next-Gen General Purpose: Real IOPS Control at Last

Introduction

Azure SQL Managed Instance has always been positioned as the lift-and-shift friendly PaaS option for SQL Server. You get high compatibility, automatic patching, built-in HA, and reduced operational overhead. For many workloads it is the easiest way to modernize without rewriting applications.

But for years, one thing held it back: storage performance. If you needed more I/O, you had to scale the entire instance. More vCores, more memory, more cost — even when CPU was not the bottleneck. Disk latency issues meant bigger SKUs, longer scale times, and higher bills.

The Next-Gen General Purpose tier, now generally available, fixes that. This is not a minor enhancement. It is a fundamental architectural shift in how storage works in Azure SQL Managed Instance.

What Actually Changed: Elastic SAN

The biggest change is invisible at first glance. Microsoft replaced the legacy page blob-based storage backend with Azure Elastic SAN.

Your data and log files no longer run on the old page blob architecture. Instead they live on a shared, high-performance SAN designed for consistent low latency and scalable throughput. Elastic SAN was built specifically to decouple storage performance from compute — and that design decision is what makes everything else possible.

The Three New Sliders: IOPS, Memory, and Storage

Next-Gen General Purpose introduced independent control over three dimensions that were previously locked together. You can now adjust any of them online without touching the others:

How the IOPS Model Works

Microsoft implemented a transparent, predictable IOPS model:

• Every instance receives 3 IOPS per GB of reserved storage for free
• Minimum free baseline is 300 IOPS per server regardless of storage size
• A 1 TB (1,024 GB) instance gets 3,072 free IOPS included in the storage price
• Additional IOPS cost: 1 IOPS = regional storage price per GB ÷ 3
• All changes are applied online — typically within 5 minutes — with no instance restart

Real-World IOPS Cost Example

Compare that to a single vCore upgrade on a 16-vCore instance — which costs hundreds of dollars per month and adds unwanted compute capacity. Adding IOPS directly is dramatically cheaper and more targeted for pure storage bottlenecks.

IOPS by vCore Count

Limitations to Know Before You Upgrade

Why This Matters to DBAs

This upgrade gives DBAs something rare in the cloud: operational control over storage that mirrors how you worked with on-premises SANs.

This is the closest Managed Instance has ever felt to running real infrastructure — with the ability to tune, measure, and adjust storage — without the operational burden of managing that infrastructure yourself.

Hands-On Workshop: Measuring and Tuning IOPS

This workshop lets you establish a baseline, identify I/O bottlenecks, tune IOPS, and validate the improvement — all without downtime.

-- Identify I/O-related waits
SELECT
    wait_type,
    wait_time_ms,
    waiting_tasks_count,
    wait_time_ms / NULLIF(waiting_tasks_count, 0) AS avg_wait_ms
FROM sys.dm_os_wait_stats
WHERE wait_type LIKE 'PAGEIOLATCH%'
   OR wait_type = 'WRITELOG'
   OR wait_type = 'IO_COMPLETION'
ORDER BY wait_time_ms DESC;

-- Read and write latency per database file
SELECT
    DB_NAME(vfs.database_id)                              AS database_name,
    mf.name                                               AS file_name,
    mf.type_desc,
    vfs.num_of_reads,
    vfs.io_stall_read_ms  / NULLIF(vfs.num_of_reads,  0) AS avg_read_ms,
    vfs.num_of_writes,
    vfs.io_stall_write_ms / NULLIF(vfs.num_of_writes, 0) AS avg_write_ms,
    vfs.io_stall_read_ms + vfs.io_stall_write_ms         AS total_io_stall_ms
FROM sys.dm_io_virtual_file_stats(NULL, NULL) vfs
JOIN sys.master_files mf
    ON vfs.database_id = mf.database_id
    AND vfs.file_id    = mf.file_id
ORDER BY total_io_stall_ms DESC;

-- Re-run after IOPS increase — compare to baseline
SELECT
    DB_NAME(vfs.database_id)                              AS database_name,
    mf.name                                               AS file_name,
    mf.type_desc,
    vfs.num_of_reads,
    vfs.io_stall_read_ms  / NULLIF(vfs.num_of_reads,  0) AS avg_read_ms,
    vfs.num_of_writes,
    vfs.io_stall_write_ms / NULLIF(vfs.num_of_writes, 0) AS avg_write_ms
FROM sys.dm_io_virtual_file_stats(NULL, NULL) vfs
JOIN sys.master_files mf
    ON vfs.database_id = mf.database_id
    AND vfs.file_id    = mf.file_id
ORDER BY avg_read_ms DESC;

Automation: Adjust IOPS with Azure CLI and ARM

IOPS changes can be scripted via the Azure REST API — useful for load testing, scheduled scaling windows, or infrastructure-as-code deployments.

Azure CLI — Update IOPS on an Existing Instance

# Adjust IOPS on an existing Next-Gen Managed Instance
# Replace values in angle brackets with your actual resource details
az rest \
  --method patch \
  --url "https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Sql/managedInstances/<instance-name>?api-version=2024-11-01-preview" \
  --body "{
    \"properties\": {
      \"storageIOps\": 8000
    }
  }"

ARM Template — Deploy New Instance with Next-Gen Enabled

{
  "type": "Microsoft.Sql/managedInstances",
  "apiVersion": "2024-11-01-preview",
  "name": "mi-nextgen-example",
  "location": "eastus",
  "sku": {
    "name": "GP_Gen5",
    "tier": "GeneralPurpose",
    "capacity": 8
  },
  "properties": {
    "storageSizeInGB": 1024,
    "isGeneralPurposeV2": true,
    "storageIOps": 8000
  }
}

Summary

Azure SQL Managed Instance Next-Gen General Purpose is one of the most operationally significant upgrades Microsoft has made to the platform. The move from page blobs to Elastic SAN is not cosmetic — it unlocks a fundamentally different model for managing database performance in Azure.

References

• Microsoft Learn – Next-Gen General Purpose Managed Instance
• Azure SQL Blog – Next-Gen General Purpose GA Announcement
• Azure SQL Blog – Introducing Next-Gen GP (Technical Deep Dive)
• Microsoft Learn – Elastic SAN Performance Overview
• Microsoft Learn – Azure SQL Managed Instance Resource Limits
• Microsoft Learn – Azure SQL Managed Instance Overview
• Azure Pricing – SQL Managed Instance