Bug #71532 Migration fails when columns are renamed
Submitted: 30 Jan 2014 17:24 Modified: 13 Mar 2014 5:45
Reporter: Stuart McGurnaghan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S3 (Non-critical)
Version:6.0.8.11354 b833 OS:Linux (Ubuntu)
Assigned to: CPU Architecture:Any
Tags: column rename

[30 Jan 2014 17:24] Stuart McGurnaghan 
Description:
When migrating from MSSQLSERVER, column names which are greater than 64 characters are renamed automatically with the object migration component. The schema creation creates the new table structure as expected, but then the bulk migration bulk data transfer attempts to import data to the original column names.

It was suggested here to rename columns after importing, but in my case the originating columns from MSSQLSERVER database are 65+ characters, so I cannot import them and cannot have the MS database schema changed.

http://forums.mysql.com/read.php?104,597087,597235

How to repeat:
Create table in MSSQLSERVER with column names greater than 64 characters and attempt full data migration of that table. I have no workaround for this at present.
[31 Jan 2014 18:15] Milosz Bodzek 
confirm, i can repeat
[11 Mar 2014 20:47] Rafael Antonio Bedoy Torres 
Posted by developer:
 
Fixed on 6.1.3.11725
[13 Mar 2014 5:45] Philip Olson 
Fixed as of the upcoming MySQL Workbench 6.1.3 release, and here's the changelog entry:

When migrating from Microsoft SQL Server, column names greater than 64
characters were automatically renamed with the object migration component.
The schema creation created the new table structure as expected, but later
the bulk migration bulk data transfer attempted to import data to the
original column names.

Thank you for the detailed bug report, it was much appreciated.