| author | MashaMSFT |
|---|---|
| ms.author | mathoma |
| ms.reviewer | randolphwest |
| ms.date | 01/23/2026 |
| ms.service | virtual-machines |
| ms.topic | include |
| ms.custom |
- Before choosing a VM size, configure your storage. Collect a baseline from your source environment under the highest stress conditions and then configure your storage based on the IOPS and throughput needs of your workload with a 20% buffer for future growth.
- Identify workload performance characteristics (OLTP vs OLAP, workload size) to determine the appropriate VM size for your business.
- If you're migrating to Azure, assess migration readiness to find the right VM size for your existing SQL Server workload, and then migrate with Azure Database Migration Service.
- Use Azure Marketplace images to deploy your SQL Server VMs as the SQL Server settings and storage options are configured for optimal performance.
- Use VM sizes with 4 or more vCores.
- Use memory optimized virtual machine sizes for the best performance of SQL Server workloads.
- The Mbdsv3-series offers the best overall performance for mission critical OLTP and data warehouse workloads.
- The Ebdsv5-series provides the best price-performance for most production SQL Server workloads.
- The Easv7-series and Msv3/Mdsv3-series are optimized for memory-intensive workloads.
- The M-series family offers the highest memory configurations in Azure for the largest workloads.
- Start development environments with the lower-tier D-Series, or B-Series, and grow your environment over time.
- Check VM supportability to avoid unsupported configurations.
- Use VM vCore customization to appropriately allocate vCPUs for your workload and VM and reduce SQL Server licensing costs, as well as disable SMT/hyperthreading settings for optimal SQL Server performance.