Edit

Share via

Create an Azure SQL assessment

  • Article

As part of your migration journey to Azure, you assess your on-premises workloads to measure cloud readiness, identify risks, and estimate costs and complexity. This article shows you how to assess discovered SQL instances in preparation for migration to Azure SQL, using the Azure Migrate: Discovery and assessment tool.

Before you start

  • Make sure you've created an Azure Migrate project and have the Azure Migrate: Discovery and assessment tool added.
  • To create an assessment, you need to set up an Azure Migrate appliance for VMware, Hyper-V or Physical environment, whichever applicable. The appliance discovers on-premises servers, and sends metadata and performance data to Azure Migrate. Learn more.

Azure SQL assessment overview

You can create an Azure SQL assessment with sizing criteria as Performance-based or As on-premises.

Sizing criteria Details Data
As on-premises Assess based on SQL Server configuration data/metadata. The recommended Azure SQL configuration is based on the on-premises SQL Server configuration, which includes cores allocated, total memory allocated and database sizes. This can be useful when the workload characteristics require a longer duration to capture a comprehensive performance metric profile.
Performance-based Assess based on collected performance data. The recommended Azure SQL configuration is based on performance data of SQL Server instances and databases, which includes CPU usage, core counts, database file organization and size, file IOs, and memory usage by each database. You can get optimal recommendations that are right-sized for the SQL workload.

Learn more about Azure SQL assessments.

Run an assessment

Run an assessment as follows:

  1. On the Overview page > Servers, databases and web apps, select Assess and migrate servers.

    Screenshot of Overview page for Azure Migrate.

  2. In Azure Migrate: Discovery and assessment, select Assess and choose the assessment type as Azure SQL.

    Screenshot of Dropdown to choose assessment type as Azure SQL.

  3. In Assess servers, the assessment type is pre-selected as Azure SQL and the discovery source is defaulted to Servers discovered from Azure Migrate appliance.

  4. Select Edit to review the assessment settings. Screenshot of Edit button from where assessment settings can be customized.

  5. In Assessment settings, set the necessary values or retain the default values:

    Section Setting Details
    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 to help 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 to help 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. For example, consider a comfort factor of 2 for effective utilization of 2 Cores. In this case, the assessment considers the effective cores as 4 cores. Similarly, for the same comfort factor and an effective utilization of 8 GB memory, the assessment considers effective memory as 16 GB.
    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.

  6. Select Save if you made changes.

  7. In Assess Servers, select Next.

  8. In Select servers to assess > Assessment name > specify a name for the assessment.

  9. In Select or create a group > select Create New and specify a group name.

    Screenshot of Location of New group button.

  10. Select the appliance and select the servers you want to add to the group and select Next.

  11. In Review + create assessment, review the assessment details, and select Create Assessment to create the group and run the assessment.

  12. After the assessment is created, go to Servers, databases and web apps > Azure Migrate: Discovery and assessment, select the number next to Azure SQL assessment. If you do not see the number populated, select Refresh to get the latest updates.

    Screenshot of Navigation to created assessment.

  13. Select the assessment name, which you wish to view.

Note

As Azure SQL assessments are performance-based assessments, we recommend that you wait at least a day after starting discovery before you create an assessment. This provides time to collect performance data with higher confidence. If your discovery is still in progress, the readiness of your SQL instances will be marked as Unknown. Ideally, after you start discovery, wait for the performance duration you specify (day/week/month) to create or recalculate the assessment for a high-confidence rating.

Review an assessment

To view an assessment:

  1. In Servers, databases and web apps > Azure Migrate: Discovery and assessment, select the number next to Azure SQL assessment.

  2. Select the assessment name, which you wish to view. As an example(estimations and costs, for example, only):

    Screenshot of Overview of SQL assessment.

  3. Review the assessment summary. You can also edit the assessment settings or recalculate the assessment.

Review support status

The assessment summary displays the support status of the database instance licenses.

  1. Select the graph in the Supportability section to view a list of the assessed VMs.
  2. The Database instance license support status column displays the support status of the Operating system, whether it is in mainstream support, extended support, or out of support. Selecting the support status opens a pane on the right which shows the type of support status, duration of support, and the recommended steps to secure their workloads.
    • To view the remaining duration of support, that is, the number of months for which the license is valid, select Columns > Support ends in > Submit. The Support ends in column displays the duration in months.

Discovered entities

This indicates the number of SQL servers, instances, and databases that were assessed in this assessment.

SQL Server migration scenarios

This indicates the different migration strategies that you can consider for your SQL deployments. You can review the readiness for target deployment types and the cost estimates for SQL Servers/Instances/Databases that are marked ready or ready with conditions:

  1. Recommended deployment: This is a strategy where an Azure SQL deployment type that is the most compatible with your SQL instance. It is the most cost-effective and is recommended. Migrating to a Microsoft-recommended target reduces your overall migration effort. If your instance is ready for SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database, the target deployment type, which has the least migration readiness issues and is the most cost-effective is recommended. You can see the SQL Server instance readiness for different recommended deployment targets and monthly cost estimates for SQL instances marked Ready and Ready with conditions.

    • You can go to the Readiness report to:
      • Review the recommended Azure SQL configurations for migrating to SQL Server on Azure VM and/or Azure SQL databases and/or Azure SQL Managed Instances.
      • Understand details around migration issues/warnings that you can remediate before migration to the different Azure SQL targets. Learn More.
    • You can go to the cost estimates report to review cost of each of the SQL instance after migrating to the recommended deployment target.

    Note

    In the recommended deployment strategy, migrating instances to SQL Server on Azure VM is the recommended strategy for migrating SQL Server instances. When the SQL Server credentials are not available, the Azure SQL assessment provides right-sized lift-and-shift, that is, Server to SQL Server on Azure VM recommendations.

  2. Migrate all instances to Azure SQL MI: In this strategy, you can see the readiness and cost estimates for migrating all SQL Server instances to Azure SQL Managed Instance.

  3. Migrate all instances to SQL Server on Azure VM: In this strategy, you can see the readiness and cost estimates for migrating all SQL Server instances to SQL Server on Azure VM.

  4. Migrate all servers to SQL Server on Azure VM: In this strategy, you can see how you can rehost the servers running SQL Server to SQL Server on Azure VM and review the readiness and cost estimates. Even when SQL Server credentials are not available, this report will provide right-sized lift-and-shift, that is, "Server to SQL Server on Azure VM" recommendations. The readiness and sizing logic is similar to Azure VM assessment type.

  5. Migrate all SQL databases to Azure SQL Database In this strategy, you can see how you can migrate individual databases to Azure SQL Database and review the readiness and cost estimates.

Review readiness

You can review readiness reports for different migration strategies:

  1. Select the Readiness report for any of the migration strategies.

    Screenshot with Details of Azure SQL readiness

  2. Review the readiness columns in the respective reports:

    Migration strategy Readiness Columns (Respective deployment target)
    Recommended MI readiness (Azure SQL MI), VM readiness (SQL Server on Azure VM), DB readiness (Azure SQL DB).
    Instances to Azure SQL MI MI readiness (Azure SQL Managed Instance)
    Instances to SQL Server on Azure VM VM readiness (SQL Server on Azure VM).
    Servers to SQL Server on Azure VM Azure VM readiness (SQL Server on Azure VM).
    Databases to Azure SQL DB DB readiness (Azure SQL Database)

  3. Review the readiness for the assessed SQL instances/SQL Servers/Databases:

    • Ready: The instance/server is ready to be migrated to SQL Server on Azure VM/Azure SQL MI/Azure SQL DB without any migration issues or warnings.
      • Ready: The instance is ready to be migrated to Azure VM/Azure SQL MI/Azure SQL DB without any migration issues but has some migration warnings that you need to review. You can select the hyperlink to review the migration warnings and the recommended remediation guidance.
    • Ready with conditions: The instance/server has one or more migration issues for migrating to Azure VM/Azure SQL MI/Azure SQL DB. You can select on the hyperlink and review the migration issues and the recommended remediation guidance.
    • Not ready: The assessment could not find a SQL Server on Azure VM/Azure SQL MI/Azure SQL DB configuration meeting the desired configuration and performance characteristics. Select the hyperlink to review the recommendation to make the instance/server ready for the desired target deployment type.
    • Unknown: Azure Migrate can't assess readiness, because the discovery is in progress or there are issues during discovery that need to be fixed from the notifications blade. If the issue persists, contact Microsoft support.

  4. Select the instance name and drill-down to see the number of user databases, instance details including instance properties, compute (scoped to instance) and source database storage details.

  5. Click the number of user databases to review the list of databases and their details.

  6. Click review details in the Migration issues column to review the migration issues and warnings for a particular target deployment type.

Review cost estimates

The assessment summary shows the estimated monthly compute and storage costs for Azure SQL configurations corresponding to the recommended SQL Server on Azure VM and/or Azure SQL Managed Instances and/or Azure SQL Database deployment type.

  1. Review the monthly total costs. Costs are aggregated for all SQL instances in the assessed group.

    • Cost estimates are based on the recommended Azure SQL configuration for an instance/server/database.

    • Estimated total(compute and storage) monthly costs are displayed. As an example:

      Screenshot of cost details.

    • The compute and storage costs are split in the individual cost estimates reports and at instance/server/database level.

  2. You can drill down at an instance level to see Azure SQL configuration and cost estimates at an instance level.
  3. You can also drill down to the database list to review the Azure SQL configuration and cost estimates per database when an Azure SQL Database configuration is recommended.

Review confidence rating

Azure Migrate assigns a confidence rating to all Azure SQL assessments based on the availability of the performance/utilization data points needed to compute the assessment for all the assessed SQL instances and databases. Rating is from one star (lowest) to five stars (highest). The confidence rating helps you estimate the reliability of size recommendations in the assessment. Confidence ratings are as follows:

Data point availability Confidence rating
0%-20% 1 star
21%-40% 2 stars
41%-60% 3 stars
61%-80% 4 stars
81%-100% 5 stars

Learn more about confidence ratings.

Next steps