Released: Data Migration Assistant (DMA) v3.0


The Data Migration Assistant (DMA) enables you to upgrade to a modern data platform by detecting compatibility issues that can impact database functionality on your new version of SQL Server. It recommends performance and reliability improvements for your target environment. It also allows you to not only move your schema, data, but also uncontained objects from your source server to your target server.

DMA replaces all previous versions of the SQL Server Upgrade Advisor and should be used for upgrades for most SQL Server versions (see below for supported versions).

What's new in v3.0?

DMA enables assessment of your on-premises SQL Server instance migrating to Azure SQL databases.  The assessment workflow helps you to detect the following issues that can affect your Azure SQL database migration.

  • Migration blocking issues
  • Partially or unsupported features and functions.

The new Azure SQL database assessment also provides comprehensive recommendations that helps fix the issues reported.

Existing features

Data Migration Assistant (DMA) v2.1

Data Migration Assistant (DMA) v2.0

Data Migration Assistant (DMA) v1.0

Supported source and target versions

Source: SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016
Target: SQL Server 2012, SQL Server 2014, SQL Server 2016, and Azure SQL Database


You can install the tool from Microsoft Download Center. Execute DataMigrationAssistant.msi to install Data Migration Assistant.



Comments (9)

  1. Avinash Rama says:

    Unfortunately V3.0 does not work as well as V2.1. Feature Recommendations are not exported, when exporting the report to CSV:”Feature parity advisor not selected, so no server instance analysis was performed.” This is after selecting “New Features’ recommendations” tick box when performing an assessment,

    1. Harini Gupta says:

      Hi Avinash,

      Thank you for using DMA and sorry to hear about the issues you have encountered.

      Feature Recommendations report is available only for on-prem SQL Server assessments. Feature Parity analysis has been introduced in DMA 3.0 for Azure DB assessments. It sounds like you are seeing a row entry for “Feature parity” when you export to CSV. Since Feature Parity isn’t supported in DMA for on-prem SQL, you will not see a list of items against it. What you are seeing in the excel report accurately reflects that behavior but I understand it throws off from your user perspective.
      We’ll have the row entry in csv removed for SQL Server assessments since it is not relevant.

      Hope this helps.

  2. The database I manage uses almost 100% middle-tier generated T-SQL. I know, I hate it, but it’s what it is. So how can I test my SQL Server 2014 application’s readiness to move to SQL Server 2016 when there’s no “code” in the database? I expected to be able to run a workload trace file through the Migration Assistant but that feature is surprisingly absent. Any ideas?

    1. Harini Gupta says:

      Hi Joshua,

      Thanks for trying out DMA and posting this comment. As you mentioned, DMA doesn’t support what you are looking for. We have another tool DEA that might be of help for you scenario of running through workload traces. Here is some info on DEA:

      You can download the tool from Microsoft Download Center –

      Please give this a try and see if suits what you are looking for.

  3. For a migration the credentials used for the source db needs CONTROL SERVER permission and for the target db needs sysadmin server role.
    I’d like to use the DMA tool against databases where I do not have either of those permissions. I’d really like a mode that doesn’t require such extreme permissions. Maybe a mode that doesn’t transfer logins, or what ever it is that requires such high permissions. Please consider this option in future releases.

    1. Harini Gupta says:

      Thank you for the feedback suggestion. We will consider adding these in the future releases.

  4. Mike W says:

    Hi, first time caller…
    How may I know what DMA is actually doing during an assessment, in order to understand the impact on disk performance / server resources of running it?
    In my case there really is no good time of day to run it (e.g. database server running 60 databases, with backups etc), so I need some additional information to get approved.
    Thanks very much

  5. Satyam says:

    do you know if the upgrade advisor is intelligent enough to look within any dynamic sql to find deprecated code?

    1. Harini Gupta says:

      Thanks for your query. SSUA is deprecated for use and DMA is the incarnation of it. At the moment, DMA doesn’t do code analysis. We do have it in our backlog plan and it will be available for future releases.

Skip to main content