Released: SQL Server Migration Assistant (SSMA) v7.3


SQL Server Migration Assistant (SSMA)  for Oracle, MySQL, SAP ASE (formerly SAP Sybase ASE), DB2 and Access lets users convert database schema to Microsoft SQL Server schema, upload the schema, and migrate data to the target SQL Server (see below for supported versions).

What is new?

  • Improved quality and conversion metric with targeted fixes based on customer feedback.
  • SSMA extensibility framework exposed via
    • Export functionality to a SQL Server Data Tools (SSDT) project
      • You can now export schema scripts from SSMA as an SSDT project and use that to make additional schema changes and deploy your database.
    • Libraries that can be consumed by SSMA for performing custom conversions
      • You can now construct code that can handle custom syntax conversions and conversions that weren't previously handled by SSMA
        • Instructions on how to construct a custom converter can be found here.
        • Sample project for conversion can be downloaded here.


Supported sources and target versions

Source: For supported sources review the information on download center for each of the above SSMA v7.3 downloads
Target: SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL DB (Azure), SQLvNext CTP1 (Technical Preview)


Comments (3)

  1. Jose Antonio Pineda says:

    Hi, Can I upgrade the before projects of SSMA 7.0 to 7.3? When I try to install the 7.3 version, it says that I must to uninstall the previous version. I don´t want to lost the work done with the 7.0 version.
    Than ks.

    1. Shamik Ghosh says:

      Hi Jose,
      Yes SSMA 7.0 projects can be opened inside SSMA 7.3 without issues.


  2. Peter Mcleod says:

    Is SSMA a viable solution to migrate a suite of enterprise Oracle databases to SQL Server? This includes bespoke database designs as well as some commercial Oracle products such as Product Hub and EBS including Trading Communities Architecture (TCA). I have a potential requirement to take an existing Oracle database estate into SQL Server as-is to continue to support some bespoke applications for a period of time. Thanks.

Skip to main content