First published on MSDN on Aug 13, 2018
Authored by firstname.lastname@example.org
SQL Server Migration Assistant (SSMA) for Oracle, MySQL, SAP ASE (formerly SAP Sybase ASE), DB2, and Access allows users to convert a database schema to a Microsoft SQL Server schema, upload the schema, and then migrate data to the target SQL Server (see below for supported versions).
What is new?
- Each iteration of the SSMA tool has been enhanced with targeted fixes that improve quality and conversion metrics.
- Some of the changes that were implemented with this release include
- Partial support for migrating spatial data types from MySQL to Azure SQL Database
- Support for migrating "Continue" statements from Oracle to SQL Server
- Support in SSMA command line to alter Data Type mapping and Project Preferences
- SSMA 7.9 for Oracle, MySQL, SAP ASE and DB2 also provides the option to migrate data using SQL Server Integration Services (SSIS).
- After converting the schema, it will be possible to create an SSIS package by using the right-click context menu option:
- The Azure SQL Database connection dialog in SSMA has also been altered to specify the fully qualified server name. In previous versions of SSMA, the Azure SQL Database prefix had to be explicitly mentioned inside projects settings.
Note: With SSMA v7.4 and later versions, .Net 4.5.2 is an installation prerequisite. Extension Pack functionality is limited when installed on SQL Server for Linux, as the tester and server-side data migration features are not supported.
Supported source and target versions
Source : For supported sources, please review the information on the Download Center for each of the above SSMA v7.9 downloads.
Target : SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, Azure SQL Database and Azure SQL Data Warehouse*.
* Azure SQL Data Warehouse is supported as a target only when using SSMA for Oracle.