We are happy to announce the release of SQL Server Migration Assistant (SSMA) v 10.0. 

Overview

SQL Server Migration Assistant (SSMA) Access, DB2, MySQL, Oracle, and SAP ASE (formerly SAP Sybase ASE) allow 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).

What’s new?

The latest release of SSMA enhances the assessment and conversion capabilities of the tool with a targeted set of fixes designed to improve quality and conversion metrics. This release includes the following:

Database Migration Service Integration [Oracle] [Preview]

Azure Database Migration Service  now allows users to migrate databases from Oracle as the first heterogeneous source for SQL target workloads. This integration enables one-time data movement of Oracle tables to SQL tables through automated bulk copy activities.

Traditionally, Oracle databases are large, and client-side migration often resulted in scalability issues and frequent timeouts. This was a significant challenge and contributing highest number of support incidents for heterogenous migration scenario. With DMS integration, the benefits include:

Support for large database migrations
Retries to overcome transient errors
Scalability through additional Integration Runtime nodes
Free migration for customers

SKU Recommendation [ Oracle]

Users can now assess their Oracle workloads and generate suitable target SKU recommendations using performance data from the Automated Workload Repository (AWR). This feature addresses the gap in Database Migration Service for Oracle within Azure Data Studio, aligning with the retirement announcement of Database Migration Assessment for Oracle    

.

 Code Conversion Improvements [DB2]

Enhanced conversion of FETCH FIRST ROW ONLY syntax
Improved support for LOCATE_IN_STRING behavior
Support for range-partitioned tables in DB2-Z O/S
Better handling of the INCLUDE clause in indexes

 Global Entra ID

Users can now authenticate using Entra ID at the global SSMA project level. Subsequent connections to the SQL target will also utilize Entra ID, providing:

A more secure default authentication method
Reduced reliance on SQL authentication
Elimination of multiple authentication steps during conversion and migration

Downloads

SSMA for Access
SSMA for DB2
SSMA for MySQL
SSMA for Oracle
SSMA for SAP ASE

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 2016, SQL Server 2017, SQL Server 2019, Azure SQL Database, an Azure SQL Database managed instance

Resources

SQL Server Migration Assistant documentation

​Microsoft Tech Community – Latest Blogs –Read More