locked
Migrating Data from MySQL to SQL Server 2012 RRS feed

  • Question

  • Hi all,

    I'm Migrating a database from MySQL to SQL Server 2012, using SSMA for MySQL v5.2.1258.  I've got the schema migrated over and have resolved any migration issues (stored procedures / views), but when it comes to migrating over the data I'm just hitting a wall.

    None of the data is migrating and when the migration report is displayed every table has a red x against it's Status.  The Output box has the following:

    Data migration operation has finished.
    0 table(s) successfully migrated. 
    0 table(s) partially migrated. 
    64 table(s) failed to migrate.

    I've seen on the forum that someone else was having the same problem

    (http://social.msdn.microsoft.com/Forums/en-US/sqlservermigration/thread/b835f4b3-3d93-42a4-9b6b-d21d3dfd8dab/)

    I've set the project settings mode to default, still getting the same error and tried using both Client Side Data Migration and Server Side migration, with both giving the same result.  I've tried going through the step-by-step blog as well.

    I am doing something really stupid?  There are 64 tables, so don't really want to try doing exports from each table and importing it into the new database.

    Hope someone can help.

    Cheers

    Alex

    Monday, July 9, 2012 11:46 AM

Answers

  • Hi all,

    Updated the database name of the target database (the SQL Server database) and the issue was resolved...  Why does the case have to match on both databases?  Seems a little strange to be, but there it is.

    Cheers

    Alex

    • Marked as answer by alexmilne Monday, July 9, 2012 1:02 PM
    Monday, July 9, 2012 1:02 PM

All replies

  • Hello,

    I don’t have suggestions for you, but you can try contacting the SQL Server Migration Assistant (SSMA) Team via e-mail (accssma@microsoft.com) to see if they can provide a solution on this scenario.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Monday, July 9, 2012 12:18 PM
  • Hi all,

    Updated the database name of the target database (the SQL Server database) and the issue was resolved...  Why does the case have to match on both databases?  Seems a little strange to be, but there it is.

    Cheers

    Alex

    • Marked as answer by alexmilne Monday, July 9, 2012 1:02 PM
    Monday, July 9, 2012 1:02 PM
  • Hi,

    I ran into the same problem and solved it through this thread, thanks!

    Instead of changing the name of the database in target server, you could change the target scheme in SSMA. Worked for me.

    Cheers
    Per



    • Edited by PerSweden Wednesday, December 18, 2013 12:19 PM
    Wednesday, December 18, 2013 12:18 PM
  • Per --

    I am having the same issues migrating data. Could you describe how you "change the target scheme in SSMA"? I can't figure out how to go about doing that.

    Thanks,

    Randy

    Monday, January 13, 2014 8:32 PM