Free tools Windows power users keep installed
One-click scans. No signup required.
Size Azure Local for SQL Server from measured workload demand and service targets—not database size or a generic node template. Profile the SQL Server virtual machines, model compute, memory, storage and network together, then test the design at peak load and during maintenance or failure conditions. Microsoft’s guidance does not prescribe a universal SQL Server node count or bill of materials; use its sizing tool to identify candidate hardware and validate the final design with an Azure Local hardware OEM or systems integrator.
What does sizing SQL Server on Azure Local involve?
SQL Server runs in Windows Server or Linux virtual machines on Azure Local. The infrastructure therefore has to support the VMs’ combined workload while meeting the service’s performance and availability objectives. Microsoft’s Azure Local architecture best practices recommend sizing around workload characteristics and testing performance under expected and degraded conditions.
There is no single CPU, memory, storage or node configuration that fits every SQL Server deployment. An OLTP database, a data warehouse and an analytics workload can place different demands on the same infrastructure. Start with observed demand and desired outcomes, then select hardware that can meet those outcomes in the operating conditions the service must support.
What should you measure before choosing hardware?
Set service targets first so the design can be judged against something more meaningful than aggregate core and memory totals. Define objectives for normal and peak demand, planned maintenance, and the failure conditions the service is expected to tolerate. Measure the end-to-end path from the application through the VM and its compute, memory, network and storage.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- HPE ProLiant ML30 Gen10 Tower Server, made for small businesses and remote offices!
- Intel Xeon E-2124 Quad-Core 3.3GHz 8MB CPU, Turbo up to 4.3GHz
- Memory: 32GB (2 x 16GB) DDR4 PC4-21300 2666MHz Unbuffered Memory
- Hard Drive: 4TB (4 x 1TB) SATA III 6Gb/s SSD for Ultra Fast Storage
- HP Smart Array S100i Gen10, HP ProLiant Integrated Lights Out (iLO) 5 Standard, DVD-ROM, Embedded HP 332i Dual-Port 1Gb Ethernet Network Adapter
- Performance: latency, throughput, IOPS, concurrency, and query or transaction completion time.
- Compute: processor architecture, physical core count, clock speed and the workload’s processor demand.
- Memory: VM allocations and the workload’s memory capacity and bandwidth needs.
- Storage: required capacity as well as observed IOPS, throughput and latency.
- Network: workload traffic and the network requirements of the selected topology.
- Operating conditions: demand during overlapping peaks, backups, recovery, storage repair, rolling updates and the intended node-failure scenario.
Use representative SQL Server activity and production-like concurrency. Include VM allocations and overlapping workload peaks; an isolated workload measurement may not reflect contention when multiple VMs run together. Microsoft’s guidance calls for modeling compute, memory, storage and network as a connected system rather than sizing from CPU and memory totals alone.
How do you turn workload measurements into a candidate design?
- Define the workload and service objectives. Record the SQL Server use case, normal and peak demand, completion-time or latency objectives, and which maintenance and failure conditions must still meet those objectives.
- Profile representative activity. Measure SQL Server under realistic concurrency and capture the processor, memory, storage and network demands of the VMs. Include overlapping peaks rather than treating each VM as if it runs alone.
- Model the infrastructure dimensions together. Evaluate physical compute, memory, storage capacity and performance, and network fit as a whole. Account for placement and contention when judging how much capacity is usable.
- Reserve capacity for operations and resilience. Test whether the remaining system can meet service targets when a machine is drained for updates or when the selected failure scenario occurs. Include backup, recovery and storage repair in validation.
- Account for growth and lifecycle changes. Include forecast workload growth and retest after material changes to hardware, firmware, network, storage or workload.
- Validate against the service targets. Compare measured latency, throughput, IOPS, concurrency and completion time with the objectives under normal, peak and degraded conditions. If a target is missed, revisit the bottleneck and candidate configuration rather than relying on a larger aggregate core count alone.
This is an iterative design process: workload observations produce a candidate configuration, and testing shows whether that configuration meets the service objectives.
Rank #2
- HPE ProLiant ML30 G10 Tower Server, perfect for small businesses and remote offices!
- Intel Xeon E-2124 Quad-Core 3.3GHz 8MB CPU, Turbo up to 4.3GHz
- Memory: 64GB (4 x 16GB) DDR4 PC4-21300 2666MHz Unbuffered Memory
- Hard Drive: 8TB (4 x 2TB) 7.2K 6Gb/s SATA 3.5" Hard Drives in RAID; Embedded 332i Dual-Port 1Gb Ethernet Network Adapter
- Hard drives and memory upgrades included separately NOT installed, installation required.
How many Azure Local nodes do you need for SQL Server?
The count depends on workload demand, the selected architecture, and the reserve needed for maintenance and failures. Microsoft’s Azure Local Baseline Reference Architecture recommends reserving at least N+1 physical-machine capacity across its hyperconverged reference instance so one machine can be drained for updates while workloads continue. It describes N+2 as an additional resilience choice when the service objective includes a machine failure during an update or another event affecting two machines at once. These are capacity-planning recommendations for that reference design, not a universal minimum node count for every SQL Server deployment.
Plan and test against physical-machine capacity, not just the nominal total of VM allocations. The design must retain enough usable capacity to meet its objectives in the specified maintenance or failure state. Microsoft’s reference architecture does not establish a workload-derived SQL Server node count; determine the count by profiling the workload and validating candidate hardware under the chosen reserve.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRank #3
- Dell T7810 Precision Tower Workstation
- 2x Intel Xeon E5-2690 v4 14-Core/28 Threads 3.1GHz (3.5GHz Turbo)
- 128GB Memory DDR4 – Nvidia Quadro K620 2GB
- Add your own Hard Drives/ SSDs
- Add your own Operating System
Also confirm the limits for the actual Azure Local architecture and version. Microsoft’s versioned System requirements for Azure Local page distinguishes a maximum of 16 machines for a hyperconverged instance from 64 machines for disaggregated deployments. Those are platform-scale limits, not sizing recommendations. Check the current requirements for the configuration you intend to deploy rather than applying one architecture’s limit to another.
How should you size storage for SQL Server?
Do not size storage by capacity alone. Set targets for capacity, IOPS, throughput and latency from workload observations, then validate performance during normal activity and operational events such as backup, repair and recovery. The Azure Local baseline architecture recommends all-flash storage for high-performance or low-latency workloads and names highly transactional databases as an example.
Rank #4
When comparing storage configurations, consider how the drive type and system behavior affect the workload’s measured performance. A configuration that meets capacity needs may still miss transaction or query objectives if it does not meet the required latency, throughput or IOPS.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What does the Azure Local sizing tool tell you?
Microsoft’s baseline architecture recommends using the Azure Local sizing tool as a planning input. Its project inputs include the number and size of VMs, workload type such as SQL Server, and resiliency preferences; it returns recommended hardware solution SKUs based on those inputs.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Treat those SKUs as candidates to investigate, not proof that the resulting system will meet your workload’s service objectives. Verify that the workload profile and resilience inputs reflect your measured demand, then validate performance and support fit with the selected OEM or systems integrator.
How should you compare catalog hardware options?
Use Microsoft catalog-listed Azure Local hardware and assess each candidate against the same workload profile and service objectives. The relevant comparison is not just the total number of cores or amount of memory:
| Design dimension | What to compare |
|---|---|
| Workload performance | Measured latency, throughput, IOPS, concurrency and query or transaction completion time at normal and peak demand. |
| Maintenance and failure reserve | Whether service objectives remain achievable with the N+1 or N+2 physical-machine capacity unavailable, as applicable to the chosen architecture and service objective. |
| Storage | Capacity, drive type, IOPS, throughput, latency, and expected behavior during repair and backup. |
| Network and support | Workload traffic, supported adapters and topology, Azure Local catalog status, and the OEM’s support limits. |
| Growth and lifecycle | Forecast growth and measured performance after updates or material platform changes. |
Microsoft’s SQL Server deployment guidance for Azure Local Version 23H2 directs readers to catalog hardware and covers SQL Server deployment. Discuss your workload profile, drive types, network and support limits with the vendor or integrator before settling on a configuration.
What deployment details belong in the sizing plan?
Record the management and operating context alongside the capacity model. Microsoft describes connected and disconnected management modes for SQL Server on Azure Local in its SQL Server on Azure Local overview. Document which mode applies and account for the operational requirements of the deployment.
The deployment guidance covers OLTP, data warehousing and business intelligence, and AI or advanced analytics use cases. It also points to SQL Server installation, performance monitoring and tuning, and high-availability and hybrid-service guidance. These use cases reinforce why the workload profile—not a generic SQL Server VM template—should drive the infrastructure design.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
