This post has been republished via RSS; it originally appeared at: Microsoft Data Migration Blog articles.
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).
The latest release of SSMA enhances each “flavor” of the tool with a targeted set of fixes designed to improve quality and conversion metrics, as well as fixes that:
- Address accessibility issues
- Add basic support for 'hierarchyid' type in SQL Server
In addition, this release includes the following:
- SSMA for DB2 has been enhanced to:
- Replace TRIM function usage in z/OS discovery queries with RTRIM/LTRIM
- Allow user to specify Package Collection when connecting in “Standard mode” (defaults to NULLID)
- Add conversion for CREATE TABLE AS SELECT
- Improve conversions for global temp tables
- Fix object uniqueness check order to prioritize tables over constraints, if names collide
- Fix loading of default column values for DATE and TIMESTAMP for z/OS
- Support Unicode line feed character (aka NEL)
- Fix cursor conversion with missing RETURN TO clause
- Add support for labels and GOTO
- SSMA for Oracle has been enhanced to:
- Fix unknown return type for a function called through synonym
- Update ODP.NET to v19.3
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 SQL Data Warehouse is supported as a target only when using SSMA for Oracle.