[Updated 2/7/2012 Selina Jia - Microsoft SQL Server Migration Assistant (SSMA) for MySQL, Sybase, Oracle and Access v5.2 ]
Welcome to the official blog site of Microsoft SQL Server Migration Assistant (SSMA) Team. In this blog site we wish to share information about SSMA product family as well as general information about migration to SQL Server from competitive platforms.
SSMA is a family of products to migrate from Oracle, Sybase, MySQL and Access to SQL Server. You can migrate to [Add: SQL Server 2012], SQL Server 2008 R2, SQL Server 2008 or SQL Server 2005. SMA for Access ,SSMA for MySQL and [ Add: SSMA for Sybase] also support migration to SQL Azure.
Welcome to the SQL Server platform!
I have been using both the Sybase and Oracle SSMA tools and I love them! I did find an issue with the 4.2 Sybase SSMA. How do I report the bug to Microsoft?
We are glad SSMA tools have been helpful to you and you like them. Please send information related to the issue you are having with the tools to email@example.com.
Hi i am a student.. I installed ssma for oracle..can u pls tell me how to run the tool..
@Ram: Have a look at the videos in blogs.msdn.com/.../mysql-to-sql-server-2008-migration-workshop-video.aspx. Though they are for MySQL, SSMA product for Oracle is similar. If you have any questions feel free to email us at ssmahelp at microsoft.com.
I am migrating Data base from Oracle DB to SQL by using SSMA (SQL Server Migration assistance for Oracle) tool but after completion convert schema I getting errors on Indexes . can you please help me any one
I think this is because some udts or user define functions or producres have no conversion. SSMA didn't recognize some user define identifier.
If you can support detail errors,I think I can better understand your errors.
We are migrating Oracle to SQL. We manage to migrate some tables but others don't work. We beleive the problem came from when Column date in Oracle is Number(*,*). We tried to change the type mapping with almost every combination but it's always the same error: ORA-00905: missing keyword.
What should we do ?