SQL SERVER – Migration Assistant for Oracle, MySQL, Sybase and Access v5.2

SQL SERVER - Migration Assistant for Oracle, MySQL, Sybase and Access v5.2 birdmigration

Migration is always the challenge, it does not matter if people are migrating from one country to another country or birds are migrating from one continent to another continent or database is migrating from one platform to another platform. I remember years ago when I had to migrate our database from another platform to SQL Server, I was extremely scared but as time passed by I learned that migration is not difficult as it seems. Of course there are challenges but there are tools available to make the migration much easier than it seems.

SQL Server Migration Assistant (SSMA) is a free supported tool from Microsoft that simplifies database migration process from various other database tools to SQL Server. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing. Recent release includes a GUI client based application to manage migration process as well as SSMA extension pack to be installed on target SQL Server.

Microsoft SQL Server Migration Assistant for Oracle v5.2

Microsoft SQL Server Migration Assistant (SSMA) for Oracle is a tool to automate migration from Oracle database to SQL Server.

Microsoft SQL Server Migration Assistant for MySQL v5.2

Microsoft SQL Server Migration Assistant (SSMA) for MySQL is a tool to automate migration from MySQL database to SQL Server.

Microsoft SQL Server Migration Assistant for Sybase v5.2

Microsoft SQL Server Migration Assistant (SSMA) for Sybase is a tool to automate migration from Sybase ASE database to SQL Server or SQL Azure.

Microsoft SQL Server Migration Assistant for Access v5.2

Microsoft SQL Server Migration Assistant (SSMA) for Access is a tool to automate migration from Microsoft Access database(s) to SQL Server or SQL Azure

Reference: Pinal Dave (https://blog.sqlauthority.com)

 

Previous Post
SQL SERVER – Case Sensitive Database and Database User – Fix: Error: 15151 – Cannot find the user , because it does not exist or you do not have permission.
Next Post
SQL SERVER – Disable Guest Account – Serious Security Issue

Related Posts

No results found.

8 Comments. Leave new

  • Hi
    I have found the answer to many of my questions here in your page and I really appreciate the effort you put in sharing your valuable knowledge with us .
    This time I came across a new problem and I had a hard time finding an answer in your old posts .I hope you can guide me through this one too .
    I have two databases that can’t be connected to each other .One of them read only for reporting purposes.I can only use Email to send files from one place to another .Can you suggest me a way to sync the changes made to working db with the readonly one ?the DB is heavy so I already failed with backup-restore solution .But not many changes are made daily on records .
    I would appreciate it if you could help me with this .

    Regards

    Ensiyeh

    Reply
  • Hi Pinal,
    I have used an older version of the SS Migration Assistant for Oracle. I used it mostly just to see what data types would map between the two databases.

    Very useful post, most people do not realize that tools like this exist.
    Ernie @wcompute

    Reply
  • Hi pinal sir,

    Good morning,

    What happened today..??? we are waiting for your interesting posts…??

    Reply
  • Hi Pinal Sir,
    Really useful information.
    Thanks for sharing.

    Regard$
    Chirag Satasiya

    Reply
  • Really it is very useful article.
    Thanks a lot Pinal.

    Reply
  • Got my answer. Thanks :)

    Reply
  • Hi Pinal,

    Do we have a tool to convert data from paradox table to SQL Server?

    Reply
  • HI .. Im using SSMA to migrate an oracle to sql db but this error shoows up whe I start to migrate data… -An unexpected error occurred. Please send the log file to product support. For more information, see “Getting SSMA Assistance” in the product documentation.
    Error Message: The given key was not present in the dictionary.-

    Please help !

    Reply

Leave a Reply