Bug #75757 MS SQL 2005 Migration
Submitted: 4 Feb 2015 0:31 Modified: 4 Mar 2015 13:21
Reporter: Robert Du Gaue Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S3 (Non-critical)
Version:6.2 CE OS:Windows
Assigned to: CPU Architecture:Any
Tags: migration, stored procedures, Views

[4 Feb 2015 0:31] Robert Du Gaue
Description:
I am trying using Workbench for its Migration of MS SQL to MySQL. There is a checkbox that comes up to mark views and SPs as part of the migration. Which I checked. But they don't migrate to the DB and are still skipped. When I force creation of a migration file all the views/SPs are there, but they all have "--", the comment characters, in them. They are the original views and not converted to anything that can easily be used to import into MySQL.

Are views/stored procedures not supported in the migration? I was told to post a bug report and real cross-ref to this report.

How to repeat:
I've tried migrating MS SQL 2005 DB a couple of times, tables migrate (some warnings), but views, stored procedures, and functions are not migrated.
[4 Feb 2015 13:21] MySQL Verification Team
Thank you for the bug report. Probably still is the case of bug  http://bugs.mysql.com/bug.php?id=39555.

See below comment from there:

 [23 Oct 2008 11:14] Mike Lischke

Stored procedure cannot automatically be converted by the Migration Toolkit. This is simply not possible due to various SP languages. You have to do this manually.

For views the situation is that they usually are converted. If you have found a case where this does not happend then please provide it here so I can take a look.

[23 Oct 2008 11:20] Mike Lischke

I'm sorry, not even views can be converted automatically due to various differences in the used SQL syntax. So this is not a bug at all.
[5 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".