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.
SSMA v5.1. supports conversion to the new features in SQL Server “Denali”, including:
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.
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.