Release Announcement of SQL Server Migration Assistant (SSMA) v 10.0

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

outline

SQL Server Migration Assistant (SSMA) for Access, DB2, MySQL, Oracle, and SAP ASE (formerly SAP Sybase ASE) allows users to convert database schema to Microsoft SQL Server schema, deploy that schema, and then migrate data to the target SQL. You can do it. Server (see below for supported versions).

What is it? new?

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

Database Migration Service Integration [Oracle] [Preview]

Azure Database Migration ServiceUsers can now migrate databases from Oracle as the first heterogeneous source for SQL target workloads. This integration allows you to move one-time data from Oracle tables into SQL tables using automated bulk copy operations.

Traditionally, Oracle databases were large and client-side migrations caused scalability issues and frequent timeouts. This was a significant challenge and resulted in the highest number of support incidents for heterogeneous migration scenarios. Here are the benefits you get from DMS integration:

• Support for large-scale database migration


• Retry to overcome temporary errors


• Scalability through additional Integration Runtime nodes


• Free migration for customers

SKU Recommendation [ Oracle]

Users can now use performance data from the Automated Workload Repository (AWR) to evaluate their Oracle workloads and generate appropriate target SKU recommendations. This feature bridges the gap in Database Migration Service for Oracle within Azure Data Studio. Announcement of end of database migration evaluation for Oracle  

.

Improved transcoding [DB2]

• Improved conversion of FETCH FIRST ROW ONLY syntax


• Improved support for LOCATE_IN_STRING behavior.


• Support for range-partitioned tables in DB2-Z O/S


• Improved handling of INCLUDE clauses in indexes

 Global Entry ID

Users can now authenticate using Entra IDs at the global SSMA project level. Subsequent connections to SQL targets also utilize the Entra ID to provide:

• A more secure basic authentication method


• Reduce reliance on SQL authentication


• Eliminate multiple authentication steps during conversion and migration

download

• SSMA for access


• SSMA for DB2


• SSMA for MySQL


• SSMA for Oracle


• SSMA for SAP ASE

Supported source and target versions

source: Please review the Download Center information for each SQL Server Migration Assistant download above for a list of supported sources.

target: SQL Server 2016, SQL Server 2017, SQL Server 2019, Azure SQL Database, Azure SQL Database managed instance

resources

SQL Server Migration Assistant documentation