This post has been republished via RSS; it originally appeared at: Microsoft Data Migration Blog articles.
SQL Server Migration Assistant (SSMA) Access, DB2, MySQL, Oracle, and SAP ASE (formerly SAP Sybase ASE) allows users to convert a database schema to a Microsoft SQL Server schema, deploy the schema, and then migrate data to the target SQL Server (see below for supported versions).
The latest release of SSMA enhances each “branch” of the tool with improved naming for statements loaded from files, revamped assessments reports compatible with modern browsers and an updated Azure AD authentication mechanism which uses the authority provided by the Azure SQL database.
In addition, this release includes the following:
- SSMA for Access now ignores auto-created indexes for foreign keys
- SSMA for DB2 has been enhanced with:
- A fix for a bug related to conversion of MIN/MAX aggregate functions with date/time arguments
- A fix for a bug in VARCHAR_FORMAT emulation function when DD placeholder is used
- Improve type mappings for TIME data type
- Improve conversion of ROUND and TRUNC functions with numeric arguments
- SSMA for SAP ASE now allows you to hide system tables and views (exclude them from conversion).
- SSMA for Oracle now adds a setting to use full type specification for %type and %rowtype attributes
Supported sources and target versions
Source: For the list of supported sources, please review the information on the Download Center for each of the above SQL Server Migration Assistant downloads.
Target: SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, SQL Server 2019, Azure SQL Database, an Azure SQL Database managed instance, and Azure SQL Data Warehouse (Azure Synapse Analytics)*.
*Azure SQL Data Warehouse (Azure Synapse Analytics) is supported as a target only when using SSMA for Oracle.