Target and pricing settings |
Target location |
The Azure region to which you want to migrate. Azure SQL configuration and cost recommendations are based on the location that you specify. |
Target and pricing settings |
Environment type |
The environment for the SQL deployments to apply pricing applicable to Production or Dev/Test. |
Target and pricing settings |
Offer/Licensing program |
The Azure offer if you're enrolled. Currently, the field is Pay-as-you-go by default, which gives you retail Azure prices.
You can avail additional discount by applying reserved capacity and Azure Hybrid Benefit on top of Pay-as-you-go offer. You can apply Azure Hybrid Benefit on top of Pay-as-you-go offer and Dev/Test environment. The assessment doesn't support applying Reserved Capacity on top of Pay-as-you-go offer and Dev/Test environment. If the offer is set to Pay-as-you-go and Reserved capacity is set to No reserved instances, the monthly cost estimates are calculated by multiplying the number of hours chosen in the VM uptime field with the hourly price of the recommended SKU. |
Target and pricing settings |
Savings options - Azure SQL MI and DB (PaaS) |
Specify the reserved capacity savings option that you want the assessment to consider, helping to optimize your Azure compute cost.
Azure reservations (1 year or 3 year reserved) are a good option for the most consistently running resources.
When you select 'None', the Azure compute cost is based on the Pay as you go rate or based on actual usage.
You need to select pay-as-you-go in offer/licensing program to be able to use Reserved Instances. When you select any savings option other than 'None', the 'Discount (%)' and "VM uptime" settings aren't applicable. The monthly cost estimates are calculated by multiplying 744 hours with the hourly price of the recommended SKU. |
Target and pricing settings |
Savings options - SQL Server on Azure VM (IaaS) |
Specify the savings option that you want the assessment to consider, helping to optimize your Azure compute cost.
Azure reservations (1 year or 3 year reserved) are a good option for the most consistently running resources.
Azure Savings Plan (1 year or 3 year savings plan) provide additional flexibility and automated cost optimization. Ideally post migration, you could use Azure reservation and savings plan at the same time (reservation is consumed first), but in the Azure Migrate assessments, you can only see cost estimates of 1 savings option at a time.
When you select 'None', the Azure compute cost is based on the Pay as you go rate or based on actual usage.
You need to select pay-as-you-go in offer/licensing program to be able to use Reserved Instances or Azure Savings Plan. When you select any savings option other than 'None', the 'Discount (%)' and "VM uptime" settings aren't applicable. The monthly cost estimates are calculated by multiplying 744 hours in the VM uptime field with the hourly price of the recommended SKU. |
Target and pricing settings |
Currency |
The billing currency for your account. |
Target and pricing settings |
Discount (%) |
Any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%. |
Target and pricing settings |
VM uptime |
Specify the duration (days per month/hour per day) that servers/VMs run. This is useful for computing cost estimates for SQL Server on Azure VM where you're aware that Azure VMs might not run continuously. Cost estimates for servers where recommended target is SQL Server on Azure VM are based on the duration specified. Default is 31 days per month/24 hours per day. |
Target and pricing settings |
Azure Hybrid Benefit |
Specify whether you already have a Windows Server and/or SQL Server license or Enterprise Linux subscription (RHEL and SLES). Azure Hybrid Benefit is a licensing benefit that helps you to significantly reduce the costs of running your workloads in the cloud. It works by letting you use your on-premises Software Assurance-enabled Windows Server and SQL Server licenses on Azure. For example, if you have a SQL Server license and they're covered with active Software Assurance of SQL Server Subscriptions, you can apply for the Azure Hybrid Benefit when you bring licenses to Azure. |
Assessment criteria |
Sizing criteria |
Set to Performance-based by default, which means Azure Migrate collects performance metrics pertaining to SQL instances and the databases managed by it to recommend an optimal-sized SQL Server on Azure VM and/or Azure SQL Database and/or Azure SQL Managed Instance configuration.
You can change this to As on-premises to get recommendations based on just the on-premises SQL Server configuration without the performance metric based optimizations. |
Assessment criteria |
Performance history |
Indicate the data duration on which you want to base the assessment. (Default is one day) |
Assessment criteria |
Percentile utilization |
Indicate the percentile value you want to use for the performance sample. (Default is 95th percentile) |
Assessment criteria |
Comfort factor |
Indicate the buffer you want to use during assessment. This accounts for issues like seasonal usage, short performance history, and likely increases in future usage. |
Assessment criteria |
Optimization preference |
Specify the preference for the recommended assessment report. Selecting Minimize cost would result in the Recommended assessment report recommending those deployment types that have least migration issues and are most cost effective, whereas selecting Modernize to PaaS would result in Recommended assessment report recommending PaaS(Azure SQL MI or DB) deployment types over IaaS Azure(VMs), wherever the SQL Server instance is ready for migration to PaaS irrespective of cost. |
Azure SQL Managed Instance sizing |
Service Tier |
Choose the most appropriate service tier option to accommodate your business needs for migration to Azure SQL Managed Instance:
Select Recommended if you want Azure Migrate to recommend the best suited service tier for your servers. This can be General purpose or Business critical.
Select General Purpose if you want an Azure SQL configuration designed for budget-oriented workloads.
Select Business Critical if you want an Azure SQL configuration designed for low-latency workloads with high resiliency to failures and fast failovers. |
Azure SQL Managed Instance sizing |
Instance type |
Defaulted to Single instance. |
Azure SQL Managed Instance sizing |
Pricing Tier |
Defaulted to Standard. |
SQL Server on Azure VM sizing |
VM series |
Specify the Azure VM series you want to consider for SQL Server on Azure VM sizing. Based on the configuration and performance requirements of your SQL Server or SQL Server instance, the assessment recommends a VM size from the selected list of VM series. You can edit settings as needed. For example, if you don't want to include D-series VM, you can exclude D-series from this list. As Azure SQL assessments intend to give the best performance for your SQL workloads, the VM series list only has VMs that are optimized for running your SQL Server on Azure Virtual Machines (VMs). Learn more. |
SQL Server on Azure VM sizing |
Storage Type |
Defaulted to Recommended, which means the assessment recommends the best suited Azure Managed Disk based on the chosen environment type, on-premises disk size, IOPS and throughput. |
Azure SQL Database sizing |
Service Tier |
Choose the most appropriate service tier option to accommodate your business needs for migration to Azure SQL Database:
Select Recommended if you want Azure Migrate to recommend the best suited service tier for your servers. This can be General purpose or Business critical.
Select General Purpose if you want an Azure SQL configuration designed for budget-oriented workloads.
Select Business Critical if you want an Azure SQL configuration designed for low-latency workloads with high resiliency to failures and fast failovers. |
Azure SQL Database sizing |
Instance type |
Defaulted to Single database. |
Azure SQL Database sizing |
Purchase model |
Defaulted to vCore. |
Azure SQL Database sizing |
Compute tier |
Defaulted to Provisioned. |
High availability and disaster recovery properties |
Disaster recovery region |
Defaulted to the cross-region replication pair of the Target Location. In the unlikely event that the chosen Target Location doesn't yet have such a pair, the specified Target Location itself is chosen as the default disaster recovery region. |
High availability and disaster recovery properties |
Multi-subnet intent |
Defaulted to Disaster recovery.
Select Disaster recovery if you want asynchronous data replication where some replication delays are tolerable. This allows higher durability using geo-redundancy. In the event of failover, data that hasn't yet been replicated might be lost.
Select High availability if you desire the data replication to be synchronous and no data loss due to replication delay is allowable. This setting allows assessment to leverage built-in high availability options in Azure SQL Databases and Azure SQL Managed Instances, and availability zones and zone-redundancy in Azure Virtual Machines to provide higher availability. In the event of failover, no data is lost. |
High availability and disaster recovery properties |
Internet Access |
Defaulted to Available.
Select Available if you allow outbound internet access from Azure VMs. This allows the use of Cloud Witness which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines.
Select Not available if the Azure VMs have no outbound internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. |
High availability and disaster recovery properties |
Async commit mode intent |
Defaulted to Disaster recovery.
Select Disaster recovery if you're using asynchronous commit availability mode to enable higher durability for the data without affecting performance. In the event of failover, data that hasn't yet been replicated might be lost.
Select High availability if you're using asynchronous commit data availability mode to improve availability and scale out read traffic. This setting allows assessment to leverage built-in high availability features in Azure SQL Databases, Azure SQL Managed Instances, and Azure Virtual Machines to provide higher availability and scale out. |