What's Changing
Azure SQL Managed Instance's Business Critical tier now supports memory right-sizing, entering public preview in early May 2026. This optimization enables you to achieve equivalent or better performance with reduced memory allocation—eliminating the overprovisioning that many teams currently accept as unavoidable.
The feature addresses a long-standing operational challenge: Business Critical instances historically required fixed memory allocations tied to licensing costs, regardless of actual workload demand. With memory right-sizing, the compute layer can now dynamically adjust how much of the allocated memory is actively used, improving performance predictability while reducing your total cost of ownership.
Who's Affected & When
Affected Products: Azure SQL Managed Instance, Business Critical service tier only.
Availability: Early May 2026 onwards, available in most Azure regions where Business Critical Managed Instance is offered. Check regional availability at https://azure.microsoft.com/updates?id=560283.
Rollout: Opt-in preview. No automatic enablement on existing instances. You must explicitly configure memory right-sizing on a per-instance basis. This means zero breaking changes—your existing deployments continue operating with current memory allocations until you choose to participate in the preview.
License Impact: The preview applies to Business Critical instances under any licensing model (License Included, Hybrid Benefit, or pay-as-you-go). No new license requirements are introduced.
What This Means for Your Environment
Operational Impact
If your Business Critical Managed Instance is currently running at sustained memory utilization below 80%, memory right-sizing offers immediate value. The feature allows the database engine to release underutilized memory back to the host hypervisor, reducing the effective footprint without sacrificing performance.
However, this is not a cost-reduction mechanism in terms of licensing. You still pay for the peak allocated memory tier. The benefit is performance consistency: fewer memory pressure events, reduced garbage collection pauses, and more predictable query execution times.
What You Should Do Right Now
- Audit your current Business Critical instances. Extract memory utilization data from the past 30 days using Azure Monitor or Extended Events. Instances with sustained utilization below 60% are the best candidates for testing.
- Identify a non-production instance. Create a test Managed Instance in the Business Critical tier (or use an existing dev/UAT instance). This is where you'll enable memory right-sizing first.
- Document your baseline performance. Capture query execution times, index seek/scan ratios, and memory-related wait stats (
RESOURCE_SEMAPHORE,PAGEIOLATCH_*) before enabling the preview. - Check regional prerequisites. Verify that memory right-sizing is available in the Azure region where your Managed Instance is deployed. If your region is not in the preview scope, you'll need to either migrate or wait for broader rollout.
Breaking Changes & Caveats
No breaking changes to application code. Memory right-sizing is transparent to applications. Connection strings, T-SQL syntax, and credential requirements remain unchanged.
Preview limitations:
- Feature may be withdrawn or modified before general availability. Microsoft support teams may not have specialized troubleshooting paths for memory right-sizing issues yet.
- Some workload patterns (very high burst memory demand) may show unexpected latency spikes if the dynamic allocation cannot keep pace. Test query patterns that trigger memory-intensive operations (large sorts, hash joins on wide tables).
- Backup and restore operations are not affected, but recovery time objectives (RTO) during memory reallocation may vary. Test your failover and restore procedures in the preview environment.
Top Resource Consuming Queries report to identify outliers.
Action Items
-
Check if Business Critical tier is in use.
Query your Azure subscription to identify all SQL Managed Instance deployments using the Business Critical service objective. Use the Azure portal or Azure CLI:
az sql mi list --query "[?serviceTierAdvisors[0].serviceLevelObjective=='BusinessCritical']" -o table -
Reserve a test instance.
If you don't have a dedicated preview/dev Managed Instance, create one now. Use the same vCPU count and generation as your production instance for accurate performance comparison. This should be a throwaway environment.
-
Enable memory right-sizing on test instance.
Via Azure portal: navigate to your test Managed Instance > Configuration > Advanced Settings > toggle Memory Right-Sizing. Or use Azure CLI (exact cmdlet subject to preview API; consult your account team for early access beta documentation).
-
Run your standard workload.
Replay production query patterns, load tests, and batch jobs for a minimum of 7 days. Monitor memory allocation graphs, query execution plans, and wait statistics.
-
Compare metrics: baseline vs. right-sized.
Create a spreadsheet tracking: CPU utilization, average query duration, 95th percentile query duration, number of memory-related waits, and backup/restore duration. Identify any regression.
-
If baseline tests pass, plan production rollout.
Coordinate with your change advisory board. Memory right-sizing should be rolled out during a maintenance window, even though it's non-disruptive, because the performance profile may shift. Have a rollback plan (disable the feature) in case unexpected issues emerge in the first 24 hours.
-
Document your findings.
Publish an internal runbook: when to use memory right-sizing, how to monitor it, and troubleshooting paths. Share with database teams and application owners.
Key Metrics to Monitor
| Metric | Baseline (Fixed) | Expected with Right-Sizing | Red Flag |
|---|---|---|---|
| Memory Utilization % | 60–85% | 40–70% (lower due to dynamic release) | >90% sustained |
| Query Duration P95 | Baseline ± 5% | Baseline (or improved) | +15% or higher |
| RESOURCE_SEMAPHORE Waits | Baseline count | ≥30% reduction expected | Increase or unchanged |
| Backup Duration | Baseline | Within ±10% baseline | Exceeds baseline by >10% |
| Plan Cache Hit Ratio | Stable | Stable or higher | Drops >5% points |
Common Questions
Does memory right-sizing reduce my Azure SQL licensing costs?
No. You continue to pay for your allocated memory tier (e.g., 128 GB Business Critical = same price). Right-sizing improves performance consistency, not price per se. However, the improved stability may allow you to consolidate fewer high-performing instances, which indirectly reduces total TCO.
Can I disable memory right-sizing after enabling it?
Yes. You can toggle the feature off at any time via the Azure portal or API. Performance will revert to fixed memory behavior within minutes. No data loss or downtime required.
Does this apply to Standard or General Purpose tiers?
Currently, memory right-sizing is limited to the Business Critical service tier. No timeline announced for extension to other tiers.
What happens if my workload suddenly demands more memory?
The right-sizing algorithm monitors memory pressure continuously. If demand spikes, the system will re-allocate memory back to the instance dynamically. In the preview, this reallocation may introduce a brief latency spike (typically sub-second), but queries will not be rejected.
