locked
SSMA for MySQL v5.2 does not show all my MySQL tables RRS feed

  • Question

  • --- comment ---

    I am starting a new thread for a question that has already been started because the earlier thread is marked as "answered," but it was not in fact answered.   There were several people in the earlier thread who said thay had this problem.  Here is the earlier thread: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ffa8c8af-f747-4c32-9bf1-9ebdd78a4742/ssma-for-mysql-v52-does-not-show-all-my-mysql-tables?forum=sqlservermigration

    --- end comment ---

    I don't see all my MySQL tables inside SSMA 5.2 after connecting to the MySQL server and database. Some tables are shown but many are not.

    All tables are Innodb in mysql and in the same database.  I can see the tables using many tools, such as MySQL Workbench.  I also have a linked server in SQL Server 2012 that links to the same MySQL server and database and sees all the tables -but SSMA 5.2 does not.  The LinkedServer uses the same ODBC connection, and the same credentials (username / password).

    I have SSMA for MySQL Extension Pack installed, and I am using  “Server Side Data Migration Engine” to migrate the tables.  I have done a "check table" from within MySQL on one of the missing tables, and there is no corruption.

    I tried to use the LinkedServer to connect from within SSMA, but it appears that SSMA does not allow me to use them????


    I have an ODBC connection with both the 32 big and the 64 bit driver.  I'm running this from 64 bit Windows Server 2012.
    • Edited by dsa42x Thursday, October 31, 2013 3:17 PM
    Thursday, October 31, 2013 2:57 PM

Answers

  • I just heard from MS support on this.  It is a known bug, existing for several versions of SSMA.  Their suggested workaround: use SQL Server 2012 Import/Export Wizard.  After my initial investigations into this, it appears to be a more superior solution than SSMA.  I/E Wizard build SSIS jobs, and I'm told the SSIS jobs can be saved and edited by developers.
    • Marked as answer by dsa42x Thursday, October 31, 2013 5:09 PM
    Thursday, October 31, 2013 5:09 PM

All replies

  • I just heard from MS support on this.  It is a known bug, existing for several versions of SSMA.  Their suggested workaround: use SQL Server 2012 Import/Export Wizard.  After my initial investigations into this, it appears to be a more superior solution than SSMA.  I/E Wizard build SSIS jobs, and I'm told the SSIS jobs can be saved and edited by developers.
    • Marked as answer by dsa42x Thursday, October 31, 2013 5:09 PM
    Thursday, October 31, 2013 5:09 PM
  • I am using SSMA to also figure out the potential issues with Stored Procedure conversion. If a stored procedure is using a table that doesn't get pulled in, SSMA is throwing up unnecessary errors because it can't find the table. For now I am ignoring such errors but it would have been nice not to face these errors. Also, in my case, only first 20 tables are being pulled in.
    Friday, May 9, 2014 8:23 PM
  • I had this same problem, the SSMA 6.0 failed to bring 80 of 250 tables and even gave foreign key error on report by the absence of these tables. I believe it really is a bug. What I did was click the right button on the database and select the "Refresh from database". So he identified the new tables and charged to the project.
    Tuesday, September 1, 2015 5:49 PM