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

Announcing SQL Server Migration Assistant (SSMA) v.5.1

Announcing SQL Server Migration Assistant (SSMA) v.5.1

  • Comments 13

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 ssmahelp@microsoft.com.

Resources:

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

  • IBM DB2 to SQL ?

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

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

  • 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 social.msdn.microsoft.com/.../4df978b6-077b-4556-b52d-8ceca3a397ab

  • 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.

  • 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 10.2.0.4.0 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.  

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

  • 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 support.microsoft.com/.../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 ssmahelp@microsoft.com with the log file.

    I hope that helps.

    -Sam

  • 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.

    Thanks,

    -Peter

  • 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?

    Thanks

    Igor

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

  • Hi, has anyone found out the fix for timeout?

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

Page 1 of 1 (13 items)
Leave a Comment
  • Please add 7 and 6 and type the answer here:
  • Post