Compartilhar via

SSMA 7.0 Adds Support for Migrating to SQL Server 2016

  • Artigo

Microsoft has released SQL Server Migration Assistant (SSMA) 7.0 which now supports migrating to SQL Server 2016 and has expanded support for Azure SQL Database.

All platforms:

  • Support for SQL Server 2016
  • Extended support for Azure SQL Database
  • Support for running SSMA on Windows 10
  • Fixed "save project" and "open project" commands for SSMA Console
  • Fixed "securepassword" command for SSMA Console
  • Fixed counting of objects for initial loading
  • Removed installer check for .Net 2.0

Oracle

  • Add conversion for in-memory tables and column store indexes to leverage In-Memory OLTP for SQL Server 2016 and In-Memory Columnstore for SQL Server 2016 and Azure SQL Database
  • Added conversion of Oracle flashback archive tables to leverage SQL Server Temporal tables in SQL Server 2016 and Azure SQL Database
  • Added conversion of Oracle VPD Policy converting to leverage Row Level Security in SQL Server 2016 and Azure SQL Database
  • Decreased time of initial loading for Oracle
  • Improved parser and resolver
  • Updated Extension Pack dependency from .Net 3.5 to .Net 4.0

Db2

  • Added conversion of DB2 in-memory tables and column store indexes to leverage In-memory OLTP for SQL Server 2016 and In-Memory Columnstore for SQL Server 2016 and Azure SQL Database
  • Added conversion of DB2 access controls to leverage SQL Server Row Level Security for SQL Server 2016 and Azure SQL Database
  • Added conversion of DB2 system-versioned tables to leverage SQL Server Temporal tables for SQL Server 2016 and Azure SQL Database
  • Improved DB2 parser and resolver
  • Removed unnecessary *.dll from Db2 installer

MySQL

  • Improved parser and resolver
  • Updated Extension Pack dependency from .Net 3.5 to .Net 4.0
  • Fixed default BigInt typemapping for MySQL
  • Fixed MsSql objects loading

MS Access

  • Fixed tables data loading for UI tabs for Access
  • Added support for disabling the loading of linked tables

Sybase ASE

  • Updated Extension Pack dependency from .Net 3.5 to .Net 4.0

To download the SSMA 7.0 release see the following links:

Comments

  • Anonymous
    July 11, 2016
    Link to SSMA for MySQL links to MS Access instead.
    • Anonymous
      July 11, 2016
      Thanks for pointing this out. It has been corrected.
  • Anonymous
    July 20, 2016
    What is the link to the forum form SSMA from MS Access? All I can find are forums with 2011 post dates.I want to learn if I can rename tables and fields during the conversion.
    • Anonymous
      July 21, 2016
      You can post on the SQL Server migration forum for this: https://social.msdn.microsoft.com/Forums/en-US/home?forum=sqlservermigration
      • Anonymous
        August 27, 2016
        Hello: We would like to migrate from an satndard SQL Server database to an Azure SQL Database, can you please post the link for SSMA for Azure SQL Database ?
        • Anonymous
          September 06, 2016
          SSMA supports both SQL Server and SQL DB migrations. When creating a new project, please select "SQL Azure" in the "Migrate to" field of the create project dialog.
  • Anonymous
    August 17, 2016
    Link to SSMA for MS Access does not work. COuld you please fix it.
    • Anonymous
      September 06, 2016
      This appears to be resolved.ThanksLonny
  • Anonymous
    September 01, 2016
    SSMA for Oracle is extremely slow. My case is Oracle 12c => Azure SQL Database. It was like takes a year to load objects. After that it takes unbelievable time just to convert objects. My database is 200 GB only, and when I convert the schema, I want to ignore index, trigger and packages which I don't need in Azure SQL Database. There's no option to rule them out even I don't need them. Seeking other methods for the migration.