Announcing SQL Server Migration Assistant (SSMA) v.5.1

Automating database migration from Oracle, Sybase, MySQL, and Access database to SQL Azure and SQL Server “Denali”.

Microsoft announced today the release of SQL Server Migration Assistant (SSMA) v.5.1, a family of products to automate database migration to all edition of SQL Server (including SQL Server Express) and SQL Azure.

What’s New in this Release?

SSMA v5.1. supports conversion to the new features in SQL Server “Denali”, including:

Free Downloads:

SSMA v5.1 is available for FREE and can be downloaded from the following:

Customers and partners can provide feedback or receive FREE SSMA technical support from Microsoft Customer Service and Support (CSS) through email at


For more information and video demonstration of SSMA and how it can help with your database migration, please visit:

Comments (15)
  1. István says:

    IBM DB2 to SQL ?

  2. Peter Tran says:

    Can you fix the Oracle utilities in SSMA so it can install against a Case Sensitive database?

  3. Jim says:

    Peter, thanks for your feedback. Do you mean Oracle extension package? We'll consider fixing it in new versions.

  4. Det says:

    Actually – correct me if I'm wrong – SQL Server 2008 Express edition doesn't have the Agent (at least, you cannot run it) preventing the use of SSMA to this type of installation.

    Can you confirm?

    See for instance…/4df978b6-077b-4556-b52d-8ceca3a397ab

  5. Jim says:

    SQL Agent is for server-side data migration. SSMA also supports client-side data migration. So it won't prevent you from migrating to express edition.

  6. TJ says:

    I have been trying to migrate a 180gb database, and it works great except on tables > 10million rows … the record counts are correct, the SSMA looks like it is migrating ok (######## of ######### rows processed) however when it comes to the end of the count, no records are migrated and the SSMA error log shows "Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding".  My migration is from Oracle 10g AIX/64 bit to SQL Server 2008 R2.  I can find no place or instruction on adjusting timeout.  I'm guessing that becasue the sql server side is processing data, the oracle side has gone idle and when sql communicates back it fails.  

  7. J2 says:

    TJ, same here. That error is from SQL server side. Have you found out solution?

  8. Sam Hughes says:

    Hi –

    I'm a PM on the SSMA team. I got this information from one of our devs.

    "The error is coming from the SQL Server side, i.e. for a command running on SQL Server, not on Oracle. There are two possible sources for it – SqlBulkCopy (i.e. timeout when writing the data) and SqlClient (i.e. timeout when reading/writing some internal status info).

    There is “Data migration timeout” option in “Project settings”->”General”->”Migration”, but it is 15 minutes per batch (by default) so should not be the root cause.

    Actually, we need a log file (with the debug level info) in order to properly investigate this issue, however user might try the following workarounds:

    • Apply…/913177.

    If installation fails saying “The upgrade patch cannot be installed by the Windows Installer Service because the program to be upgraded may be missing or the upgrade patch may be update a different version of the program…", try steps below.

    • In “Project settings”->”General”->”Migration”, switch “Parallel data migration mode” option to “Custom” and “Thread Count” to 1.

    • In “Project settings”->”General”->”Migration”, set “Batch Size” to a lower value, e.g. 1000."

    If that fails contact with the log file.

    I hope that helps.


  9. Peter Tran says:

    Hi Jim,

    I just installed the latest SSMA v5.2 Oracle extension back and I'm still getting errors during installation. Have you had a chance to fix the installer to run against a case sensitive database?

    By default, Oracle treats the data as case sensitive and the metadata as case insensitive. With SQL Server, when we want to get the same behavior (ie treating the data as case sensitive), SQL Server also treats the metadata as case sensitive.



  10. Igor Zottich says:

    I have the same timeout errors when migrating Oracle tables with a few millinon of recods in them.

    I would like to try the workouround, but before installing it, would it be possible to know what it does?



  11. sonic says:

    Hi , I am also facing the same issue. Is there any update or workaround for this issue?

  12. vinod says:

    Hi, has anyone found out the fix for timeout?

  13. vinod says:

    I have both the workaround mentioned above in Sam's comment with no luck.

  14. Miguel says:

    I have the same issue as TJ and J2 above.  I am able to migrate smaller oracle tables just fine.  But when I go above the 20 million row tables and up I get the following error:      "Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding."

    I am on:

    Windows Server 2008 R2

    SQL Server 2008 R2

    Oracle 9i on AIX 5L 64 bit

    SSMA 5.3

    Thanks in advance for any comments.

    1. Satyajeet Parida says:


      I used SSMA v5.3 for migrating a MySQL database to MS SQL server.
      Just like most of you, I was facing the timeout error while migrating a table with >30 million rows

      I tweaked the settings suggested by Sam Hughes a bit.
      Since the table size is so huge, I changed the timeout and batch size to a very high value.

      In “Project settings”->”General”->”Migration”, Data Migration Timeout is 15 minutes (by default), which I changed to a very high value like 600 minutes.
      Also in “Project settings”->”General”->”Migration”, default Bulk Copy “Batch Size” was 1000, which I changed to 50000.

      The above configuration changes worked for me.

      Hope this helps.


Comments are closed.

Skip to main content