Bug #68729 wbcopytables has a limit on # of chars it can support in select statement
Submitted: 20 Mar 2013 16:55 Modified: 25 Mar 2013 13:43
Reporter: Marc Nesheim Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S1 (Critical)
Version:5.2.47CE Rev 10398 OS:Windows (Version 7)
Assigned to: CPU Architecture:Any
Tags: migration, wbcopytable

[20 Mar 2013 16:55] Marc Nesheim
Description:
I am trying to migrate an existing MS SQL database to a MySQL server.  I have 2 tables which both have about 100 columns defined.  Each column name is about 15-25 characters long.  When I try to migrate both of these tables, I am getting an error message stating "[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name". 

When I look through the log of the migrating process, I can see that the select statement to get the data from the source database, has an incomplete list of all the column names.  The last column name that show up is actually chopped off in the middle of the actual column name.  So when the select statement is executed it is failing resulting in the above error message.

MySQL Workbench Version: 5.2.47 CE Rev: 10398

I have tried the the following ODBC Drivers and all have produced the same result:
ODBC Driver 11 of SQL Server Ver 2011.110.2270.00 from Microsoft
SQL Server Ver 6.01.7601.17514 From Microsoft
SQL Server Native Client 11.0 Ver 2011.110.2100.60 From Microsoft

Source DB: MS SQL Server 2005
Target DB: MySQL Server ver 5.5.3

How to repeat:
Use the MySQL Workbench to copy a table with many columns that have a long column names.
[25 Mar 2013 13:43] Sergio Andres De La Cruz Rodriguez
This is a duplicate of bug 68146 (http://bugs.mysql.com/bug.php?id=68146)