SQL Server Migration Assistant (SSMA) Team's Blog

How-to articles, tips-and-tricks, and guidelines for migrating from Oracle/Sybase/MySQL/Access to SQL Server and SQL Azure

Microsoft SQL Server Migration Assistant (SSMA) 5.2 is Now Available

Microsoft SQL Server Migration Assistant (SSMA) 5.2 is Now Available

Rate This
  • Comments 63

Automating Database Migration to SQL Server 2012

SQL Server Migration Assistant (SSMA) v5.2 is now available. SSMA simplifies database migration process from Oracle/Sybase/MySQL and Microsoft Access to SQL Server and SQL Azure. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing to reduce cost and reduce risk of your database migration project. 

The new version of SSMA - SSMA 5.2 provides the following major enhancements:

  • Support conversion of Oracle %ROWTYPE parameters with NULL default
  • Support conversion of Sybase’s Rollback Trigger
  • Better user credential security to support Microsoft Access Linked Tables

Download SQL Server Migration Assistant (SSMA) v.5.2

Launch the download of the SSMA for Oracle.

Launch the download of the SSMA for Sybase.

Launch the download of the SSMA for MySQL.

Launch the download of the SSMA for Access.

  • Hi Dibin,

    You use SSMA 5.2 to migrate to any edition of SQL Server. In the overview section of www.microsoft.com/.../details.aspx

    we have mentioned "SSMA for Oracle v5.2 is designed to support migration from Oracle 7.3 or later version to all edition of SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012."

  • Hi Mindy,

    I am sorry for the late reply. You can use the help section of the tool and you can also download the whitepapers from www.microsoft.com/.../details.aspx

  • Do SSMA v5.2 support migrations from Sybase ASA 12.0 or higher?

  • Hi Newbie,

    I am really sorry but unfortunately we never had Sybase ASA on our plans for SSMA. The plan is still intact and we still support migration from Sybase ASE 11.9 onwards with the latest version of SSMA for Sybase www.microsoft.com/.../details.aspx

    But I still see a silver lining in your case since your need is to migrate only schema and data I guess you can use a Linked Server to great advantage. The syntax between Sybase and MS SQL Server don’t differ much as they share the same DNA. Below are the providers that you can use to setup a linked server from SQL Server to Sybase ASE and then use queries to pull data and insert into the local database.  I am providing some information below to give you pointers for the same.  

    a) Have to install the required provider/driver on the SQL Server machine.

    Sybase ASA can be connected in following ways

    OLE DB Providers

    You need an OLE DB provider for each type of data source you wish to access. Each provider is a dynamic-link library. There are two OLE DB providers you can use to access Sybase IQ:

    Sybase ASA OLE DB provider The Adaptive Server Anywhere OLE DB provider provides access to Sybase IQ as an OLE DB data source without the need for ODBC components. The short name for this provider is ASAProv.

    When the ASAProv provider is installed, it registers itself. This registration process includes making registry entries in the COM section of the registry, so that ADO can locate the DLL when the ASAProv provider is called. If you change the  

    location of your DLL, you must reregister it.

    If you use the Adaptive Server Anywhere OLE DB provider, ODBC is not required in your deployment.

    ODBC Driver

     Microsoft OLE DB provider for ODBC Microsoft provides an OLE DB provider with a short name of MSDASQL.

    The MSDASQL provider makes ODBC data sources appear as OLE DB data sources. It requires the Sybase IQ ODBC driver.

    b) Create a Linked Server and then query the same.

    This link species the steps and some common errors while setting the Linked Server

    Steps :  sql-articles.com/.../creating-linked-server-to-sybase-from-sql-server  (These are for ASE but are the same for ASA except that you have to choose a different provider/driver)

    Issues : social.msdn.microsoft.com/.../fe29f12d-67b0-40a8-a41b-1767853a0185

  • I installed the ssma to convert mySQL to SQL Express, but, it doesn´t work. The button "convert" is not able and a message "SQL SERVER AGENT" is not ruuning. IT's obvisious thais is not running because sql express (2005) doens´t have it.

    What can I do? ivo@share.com.br

  • Hi,

    MS Access to SQL Server

    Why not support the extended property "Field Description" (of a table) and also automatically convert it ? Access and SQL Server support it both.

    Any plans to support the conversion of the multi-level Access Attach-fields ?

    best regards Klaus

  • The license key page is now 404.  I need a license file.  What is the correct URL?

  • Scott is right, license registration page is still a 404 error page... Dead in the water until I can get a license. Just sent an email to ssmahelp@microsoft.com though.

  • The very last step of Part 2 where you update the object table and cross apply with the value from cat.xml values in the tblRawData to get the conversion status throws the following errors:

    Msg 8152, Level 16, State 14, Line 1

    String or binary data would be truncated.

    The statement has been terminated.

    Msg 2627, Level 14, State 1, Line 23

    Violation of PRIMARY KEY constraint 'PK__tblSSMAR__E3B3531E2FFBD6D4'. Cannot insert duplicate key in object 'dbo.tblSSMAReport_MessageDetails'. The duplicate key value is (EnginneringConstructionProject, report, 008a49a7-91c2-4c40-a402-55768e0f3d5e, A2SS0030).

    The statement has been terminated.

    Any suggestions / solutions?

  • So I was able to resolve the string or binary data would be truncated error by modifying tblSSMAReport_Object 'Name' from Varchar(32) to Varchar(40). Now we're left with the error:

    Msg 2627, Level 14, State 1, Line 1

    Violation of PRIMARY KEY constraint 'PK__tblSSMAR__E3B3531E2FFBD6D4'. Cannot insert duplicate key in object 'dbo.tblSSMAReport_MessageDetails'. The duplicate key value is (EnginneringConstructionProject, report, 008a49a7-91c2-4c40-a402-55768e0f3d5e, A2SS0030).

    Han, do you have any suggestions?

  • Where can I obtain the license file? The link to the license file from the setup program brings me to a 404 error page.

  • On the Connect to Sql Server Window, the list of Server names is blank.  Why can't SSMA find any Sql Server instances on my machine?

  • Trying to register license produced a 500 - Internal Server Error.  Tried both Typical and Complete installation options.  Cannot register license.

  • to get a license, one should login with a live id.

  • After looking at the threads for the license piece, it's no wonder people are disliking your products.  Jeez!  Such a simple thing to give simple directions on where to install the license.  Can't find anything close to where you describe where the license should go.

    Goodbye Gates, Ballmer, and soon Microsoft....TIme to go!!!

Page 3 of 5 (63 items) 12345
Leave a Comment
  • Please add 2 and 7 and type the answer here:
  • Post