Bug #73142 MySQL Workbench migration failed to retrieve schema list from source MSSQL
Submitted: 28 Jun 2014 12:15 Modified: 7 Mar 2017 23:13
Reporter: Yule Blucky Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S3 (Non-critical)
Version:6.09/6.2.4 OS:Microsoft Windows (Win7 Pro)
Assigned to: CPU Architecture:Any

[28 Jun 2014 12:15] Yule Blucky
Description:
Trying to migrate a MSSQL database from a shared server to a MySQL database on a different shared server.

All goes well until the 'Fetch Schema List' at which point I get this text in the message log dialogue box:

Starting...

Connect to source DBMS...

- Connecting to source...

Connecting to Mssql@FantasyFootball

Opening ODBC connection to DSN=xxxxx;DATABASE=xxxx;UID=xxxx;PWD=XXXX...

Connected

Connect to source DBMS done

Check target DBMS connection...

- Connecting to target...

Check target DBMS connection done

Retrieve schema list from source....

- Checking connection...

- Fetching catalog names...

WARNING: The following catalogs where not found: fantasyfootball

- Fetching schema names...

- Finished

Retrieve schema list from source finished

Tasks finished with warnings and/or errors, view the logs for details

Finished performing tasks.

I tried to include the Help Log file here but it was deemed too long to submit as this form field has a 8k limit

How to repeat:
I found this posted in forums which is almost identical to my issue. The response from Sergio A. de la Cruz Rodríguez Software Developer Oracle Corp said to report it as a bug but I can't find out if it was reported and or fixed.
http://forums.mysql.com/read.php?104,595516,595836#msg-595836
[28 Jun 2014 12:16] Yule Blucky
Workbench Help Log

Attachment: WorkBenchHelpLog.txt (text/plain), 9.34 KiB.

[29 Jun 2014 20:34] Miguel Solorzano
Please try version 6.1.7. Thanks.
[30 Jul 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[4 Sep 2014 7:14] Peeter Marvet
This issue is possibly caused by need to have VIEW ANY DEFINITION right - as explained in http://mysqlworkbench.org/2013/08/video-tutorial-setup-a-restricted-sql-server-account-for...

As other similar tools don't have this problem it would be good to either have clear pointer to the requirement in help / error message - or provide alternative method in case of missing VIEW ANY DEFINITION.

btw, I was able to migrate the DB from MS SQL using RazorSQL (that has in DB tools "Convert database" option allowing MySQL compatible export)
[4 Sep 2014 7:23] Peeter Marvet
@Miguel Solorzano - problem is reproducable with 6.1.7.11891 build 1788 (community), using both OpenLink Express and Lite ODBC drivers on OSX and MS ODBC driver on WinXP
[20 Nov 2014 18:21] Alex Lindberg
I can browse the DB with Excel or Eclipse, but when I try to migrate the following log is displayed:

Starting...
Connect to source DBMS...
- Connecting to source...
Connecting to Mssql@Matrix Tool...
Opening ODBC connection to DSN=Matrix Tool;DATABASE=CompatMatrix;UID=Cmatrix_user;PWD=XXXX...
Connected to Mssql@Matrix Tool, 10.50.4000.0
Connect to source DBMS done
Check target DBMS connection...
- Connecting to target...
Check target DBMS connection done
Retrieve schema list from source....
- Checking connection...
- Fetching catalog names...
WARNING: The following catalogs where not found: CompatMatrix
- Fetching schema names...
- Finished
Retrieve schema list from source finished
Tasks finished with warnings and/or errors, view the logs for details
Finished performing tasks.

However no schema are displayed to complete the migration.

I am using MySQL Workbench 6.2 v 6.2.3.12312 build 2280 (64 bits) on a Win7 64bit system.
[24 Feb 2015 11:44] Miguel Solorzano
http://bugs.mysql.com/bug.php?id=76008 marked as duplicate of this one.
[24 Feb 2015 14:14] Miguel Solorzano
Please try version 6.2.4 using ODBC (native) as connection method for source. Thanks.
[25 Mar 2015 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[1 Apr 2016 18:06] Ranjodh Singh
Starting...
Connect to source DBMS...
- Connecting to source...
Connecting to Mssql@DRIVER=SQL Server Native Client 11.0;SERVER=localhost\SQLEXPRESS...
Opening ODBC connection to DRIVER={SQL Server Native Client 11.0};SERVER=localhost\SQLEXPRESS;DATABASE={etracProProd};UID=appuser;PWD=XXXX;...
Connected to Mssql@DRIVER=SQL Server Native Client 11.0;SERVER=localhost\SQLEXPRESS, 12.0.2000.8
Connect to source DBMS done
Check target DBMS connection...
- Connecting to target...
Check target DBMS connection done
Retrieve schema list from source....
- Checking connection...
- Fetching catalog names...
WARNING: The following catalogs were not found: etracProProd
- Fetching schema names...
- Finished
Retrieve schema list from source finished
Tasks finished with warnings and/or errors, view the logs for details
Finished performing tasks.

I am using 6.3 version and using ODBC (native) as connection method for source.

Please help
[4 Jul 2016 13:26] Paul Guillou
I too am getting the same issue. Workbench version 6.3.7. I am going to fiddle with db_mssql_grt.py to change sys.databases to sysdatabases on the basis that there is a table called sysdatabases in the master database. Does this sound as if I'm on the right lines? MS SQL version 8.00.2065.
[5 Jul 2016 7:17] Henk Winkel te
Affects me as well using workbench version 6.3.5 on Windows 8 64 bit icw MsSql 2014
[2 Dec 2016 5:48] lalit Choudhary
Give SELECT, CONNECT , VIEW ANY DEFINITION  privileges to MS-SQL connection and database. Afer this setting it should work fine.
There is no issue from MySQL Workbench side.
It solved my problem.
[7 Feb 2017 23:13] Miguel Solorzano
Please try version 6.3.9. Thanks.
[8 Mar 2017 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[22 Feb 21:45] Jacob Nikom
I lost my ability to retrieve the schemes once we changed the MSSQL from 2008 R2 to 2017. However, I am still able to do the data migration using wbcopytables-bin command, but the migration time became much longer.