Bug #69596 When migration SQL Server 2005 to MySQL, VARCHAR fields will be cut down

• Submitted: 27 Jun 2013 5:52
• Modified: 31 Jul 2013 15:33
• Reporter: gan li
• Status: Closed
• Category: MySQL Workbench
• Severity: S2 (Serious)
• Version: 6.0.2 beta
• OS: Windows (windows7 64)
• CPU Architecture: Any
• Tags: migration, SQLServer

[27 Jun 2013 5:52] gan li

Description:
I am trying to migrate a database from Microsoft SQL Server 2005 to a local database MySQL Server 5.6 for Win7-64.

Although the tool is able to migrate schema and data , it cut down the VARCHAR  fields data.
Like this:
sql2005: varchar(200) http://qu.test.org.cn/qu/le/g([0-9_]*)/index.html
mysql:   VARCHAR(200) http://qu.test.org.cn/qu/le/g(

When use 5.2.47 workbench no this situation， but some table VARCHAR  fields will cause the Bug #66516.

How to repeat:
migrate a database fro sql2005: varchar fields,  6.0.2 beta.

Set a varchar fields, like varchar(200) ,
add data like http://qu.test.org.cn/qu/le/g([0-9_]*)/index.html

[27 Jun 2013 13:51] Peter Laursen

Looks like 'square brackets' needs escaping somehow? In MS databases (SQL Server and Access) 'square brackets' are *identifier quotes* (working like backslash in MySQL non-ANSI mode).

Just an idea!

[27 Jun 2013 13:54] Peter Laursen

Sorry .. I meant 'backtick'/'backquote' and not 'backslash'.

[27 Jun 2013 14:18] gan li

The same when use other data.
Like this:
sql2005: varchar(200)  I am trying to migrate a database from Microsoft SQL Server 2005
Get:
mysql:   VARCHAR(200) I am trying to migrate a datab

environment： 
SQL Server 2005 64bit COLLATE Chinese_PRC_CI_AS
Mysql5.6  character-set-server=utf8

When use 5.2.47 workbench no this situation， but some table VARCHAR  fields will cause the Bug #66516.

[27 Jun 2013 20:29] Sergio Andres De La Cruz Rodriguez

Apply this patch to the db_mssql_migration_grt.py file (under the modules dir inside the MySQL Workbench install dir)

Attachment: patch_bug_69596.diff (text/x-patch), 340 bytes.

[31 Jul 2013 15:33] Philip Olson

Fixed as of MySQL Workbench 6.0.3, and here's the changelog entry:

Migrating Microsoft SQL Server to MySQL could truncate "VARCHAR" data.

Thank you for the bug report.