Identify compatibility issues
Suppose you're a database administrator for a law firm, and you've identified the SQL Server instances within your organization that require upgrading. You want to check that the databases will continue to function after migration. Your CTO is creating a report detailing the return on investment (ROI) that will be gained by moving the databases to SQL Server 2019. They want you to provide details of the features in SQL Server 2019 that will realize benefits to the users. The CTO wants to use these details to reassure partners in the firm that the investment is worthwhile.
The Microsoft Data Migration Assistant (DMA) can check each database for compatibility issues and, because a few databases are moving to Azure SQL Databases, identify functionality that won't be supported after migration. The DMA will also recommend how to use new features in the target database.
In this unit, you'll explore the DMA's functionality to identify compatibility issues, provide recommendations, and export an assessment as a report.
Identifying compatibility issues
DMA compares the SQL Server version on your source database with your intended upgrade version, and identifies breaking changes, behavior changes, and deprecated features. Use the DMA to check against an upgrade version without having to have that version installed anywhere. If you're running a feasibility study to see the impact of upgrading, you choose your target version, and run the assessment against an existing database, all without any initial setup or licensing cost.
On-premises source versions from SQL Server 2005 are supported. You select a target type of Azure SQL Database, SQL Server, and SQL Server on Azure Virtual Machine. The option you choose for the target type may determine the version of the target you can select. If your source is an on-premises SQL Server instance, you can compare against SQL Server 2012 through SQL Server 2019, including SQL Server on Linux. However, if you select Azure SQL Database or SQL Server on Azure Virtual Machine, DMA only compares against the current Azure version that's available.
You can run the assessment on one or more databases and on one or more instances. If the target is Azure SQL Database, you run the compatibility check with the performance recommendations and the SQL Server feature parity check. Or you can run each assessment individually. The size of each selected database affects the time it takes to run the assessment.
It's best practice to run assessments on a development or test version of the database. After assessments are complete, run the same checks on the production database. When you need to run the assessment in production, ensure you do it at the time of lowest activity so as not to impact users.
By default, the DMA saves each assessment project, and you can reopen the assessment to view the results. You run it again if you have made changes since the last check. DMA saves the credentials so you don't need to reconfigure the setup. You can also delete any assessments that you no longer need.
Discovering feature recommendations
The New features' recommendation assessment can be run alongside the Compatibility issues assessment, or on its own. The assessment evaluates three key areas:
Migrating your database to a newer version of SQL Server doesn't guarantee improved performance. Changes to the query engine may mean source queries don't run optimally on the target, if no changes are made to the database during or after migration. Existing indexes might no longer be sufficient, as new index enhancements can bring faster results to large datasets.
These faster results can be especially important for analyzing corporate data in real time. For example, if you're upgrading a database from SQL Server 2008 R2 to SQL Server 2019. After the DMA assesses your indexes, it could recommend dropping an existing clustered index, and replacing it with a clustered columnstore index. With the growth in data captured and stored by modern businesses, getting as much speed as possible from a database can become the main reason for a migration.
The security assessment identifies areas in your database that would benefit from new features to ensure tighter controls over sensitive data. Recommendations are categorized as High, Medium, and Low Value. For example, if you upgrade customer contact details from a SQL Server 2008 R2 database to SQL Server 2019, DMA might recommend you use Always Encrypted (AE), or Dynamic Data Masking (DDM) to secure sensitive data such as personal details. The DMA includes full instructions for using each feature it recommends.
Storage recommendations are also categorized into High, Medium, and Low Value areas. For example, DMA might suggest you use a stretch database to reduce storage costs, and recommend how to achieve this improvement. If there are any issues within the database, such as a
CHECK constraint that isn't compatible with stretch technology, DMA highlights this issue.
SQL Server feature parity
If you run your assessment against a target Azure SQL Database or SQL Server for Linux, the DMA creates a list of unsupported, and partially supported features. The Azure and Linux versions of SQL Server offer reduced functionality. It's important you do a full test before migration, otherwise your migration could result in a broken database.
Features you currently depend on in an on-premise version may not be available. DMA highlights unsupported features by the components installed on your source instance to the target. For example, at the time of release, Master Data Services (MDS), SQL Server Analysis Services (SSAS), and SQL Server Reporting Services (SSRS) aren't supported on Azure SQL, or SQL Server for Linux. Any interaction with these services would need to be removed, or redeveloped. Support for SQL Server features on Azure SQL, and SQL Server for Linux databases, will increase over time.
Partially supported features in Azure SQL Database, or SQL Server for Linux, don't have the same depth of functionality as the on-premises Windows versions. The DMA automatically finds feature discrepancies so you can plan around any potential issues.
Export assessment report
The DMA saves your assessment projects until you delete, so you can view them later. You can export the results to a CSV or JSON file, so you have a detailed list of fixes. Exports are useful for sharing with other database administrators and developers. When you have a complete list, you then plan upgrades and allocate resource for doing them.
Steps to identify compatibility issues
The three key phases when using the DMA to identify compatibility issues are:
1. Run the compatibility assessment
- In DMA, start by selecting Assessment, and provide a name for the project.
- Choose SQL Server as the Source server type and Target server type.
- Select the target server SQL Server version; it's the SQL Server version you'll be assessing for compatibility.
- During an assessment, the default is Compatibility Issues; you can also add the New features' recommendation option, and the Check feature parity option if your target is Azure SQL Database, or SQL Server 2019 for Linux.
- Select the source server instances, and connection credentials.
- You can now select Start Assessment, and when the assessment is complete, the results are displayed in the Review results tab.
2. Review the assessment results
- In the results, there's a tab for each tested version. For example, if SQL Server 2019 is a target, there will be a Compatibility 150 tab.
- For each compatibility tab, there might be a Behavior changes note, listing issues for review.
- There might also be an Impact section, with Recommendation notes, highlighting any Impacted objects list; click through the object list to see more details.
3. Export the assessment results
- To export the assessment, select Export report, and you can then choose the format to use for the export, such as CSV.
- The exported report is then viewed in Excel, or other tools, to get detailed information on issues and recommendations.
The Microsoft Data Migration Assistant automates the process of finding compatibility issues between different versions of SQL Server before upgrading a database. The assistant checks one or more databases, on one or more servers at a time. You don't need to have the target version installed. Assessment reports are saved so you can view the results later, or rerun the assessment without having to reenter credentials or select databases.
The DMA compares your database to the target version to recommend new features you can benefit from. In the rush to move from one version to another, it's easy to prioritize ensuring the database is functional, overlooking new features that enhance the performance or security of the migrated database.
You can also export the assessment results to Excel or JSON, giving you a detailed list of issues to fix before an upgrade. This list provides a clear development plan to upgrade your databases. You'll know all about compatibility problems and unsupported features in advance.