MySQL Bugs: #16186: Migration from MsSQL to MySQL cannot be done

Bug #16186	Migration from MsSQL to MySQL cannot be done
Submitted:	4 Jan 2006 14:13	Modified:	1 Jun 2006 14:37
Reporter:	Peter Lindeman	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S1 (Critical)
Version:	1.0.21rc	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
When I try to migrate from MsSQL 2005 server to MySQL 5.0.18 halfway the migration process it gets stuck.
I can select the database which I want to migrated, then the reverse engineering process starts but here something goes wrong. The last message in the messagelog is :

=========================
Routines fetched.
Could not parse XML data
=========================

When I then press the next button the next window is empty and I cannot select  any object to migrate

How to repeat:
Create a view on the MsSQL database and try to migrate. When the view is not there you can migrate. With the view in the database behaviour is as described above.

Could you please provide a script sample of the MSSQL table/view for to
migrate to MySQL because I did a simple table/view and I was unable to
get the behavior reported (the application stuck), instead I got a warning
for to need to edit manually the view and the create statement is wrong:
1. Schema Migration
-------------------

  Number of migrated schemata: 1

  Schema Name:            bugdb_dbo
  - Tables:               1
  - Views:                1
  - Routines:             0
  - Routine Groups:       0
  - Synonyms:             0
  - Structured Types:     0
  - Sequences:            0

  Details:

  - Tables
      `bugdb_dbo`.`tb1`
      -----------------
  - Views
      `bugdb_dbo`.`v_tb1`
      -------------------
          The generated SQL has to be checked manually.

-- -------------------------------------
-- Views

-- DROP VIEW IF EXISTS `bugdb_dbo`.`v_tb1`;
-- CREATE OR REPLACE VIEW `bugdb_dbo`.`v_tb1` AS
-- create view v_tb1 as select * from tb1 where col1 >= 2;

Yes please you can upload the zip file with a name like: bug16186.zip
at: ftp://ftp.mysql.com/pub/mysql/upload

Thanks in advance.

Uploaded it.

I was unable to restore your bak file with a message like:

The backup set holds a backup of a database other than the existing 'ptc_dbase_pli' database. 

I am not quite familiar with that restore tool. Any idea?

Thanks in advance.

I have used MsSQL 2005 here. 
In Microsoft SQL Server Management Studio select the database, right click it and select Tasks - Restore - Database
Select from Device and add the BAK file, check the field to restore this one. In options check the box "Overwrite the existing database"
After pressing OK the database must be restored.

Thank you for the bug report and feedback.

I was unable to repeat the behavior reported with version 1.0.25:

--------------------------------------------------------------------------------
-- MySQL Migration Toolkit Report                                             --
--                                                                            --
-- Title:   Summary Of The Migration Process                                  --
-- Date:    2006-06-01 11:36                                                  --
--------------------------------------------------------------------------------

1. Schema Migration
-------------------

  Number of migrated schemata: 1

  Schema Name:            ptc_dbase_pli_dbo
  - Tables:               43
  - Views:                1
  - Routines:             0
  - Routine Groups:       0
  - Synonyms:             0
  - Structured Types:     0
  - Sequences:            0

  Details:

  - Tables
      `ptc_dbase_pli_dbo`.`LEZERS_TABEL`
      ----------------------------------
      `ptc_dbase_pli_dbo`.`USR_DEF_OUTPUTS_TABEL`
      -------------------------------------------
      `ptc_dbase_pli_dbo`.`CHIPREADER_TERMINALS_TABEL`
      ------------------------------------------------
<cut>

This bug has resurfaced in 1.1.5rc

I tried migrating a 150 table database from MS Sqlserver 2000 to MySQL 5.0, and got the following error in Object Selection --> Check Result:

Routines fetched.
Could not parse XML data
No schematas have been reverse engineered.

I can't upload the database because it contains sensitive information.  Maybe someone could tell me where I could find more detailed logs, or the XML data that MySQL can't parse?