Bug #68084 Migration doesn't copy values greater then 127 into unsigned tinyint
Submitted: 14 Jan 2013 14:59 Modified: 13 Jun 2013 0:51
Reporter: Robin Oaks Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S2 (Serious)
Version:Workbench 5.2.45 CE OS:Windows (Windows 7 64bit)
Assigned to: CPU Architecture:Any
Tags: MySQL Workbench migration wizard, tinyint unsigned

[14 Jan 2013 14:59] Robin Oaks 
Description:
When migrating a SQL Server 2008 R2 database into MySql, the create table script properly defines a field as tinyint unsigned, but when wizard batch copies records into the table, it will not copy a value greater than 127 (the max for a signed tinyint). Thus, throwing an exception and not copying that batch and subsequent batches of records.

How to repeat:
Using Migration Wizard On Windows 7 64-bit, migrate a SQL Server 2008 R2 database table that has field of unsigned tinyint and record values of greater than 127 in that field.
[23 Jan 2013 14:48] MySQL Verification Team 
Thank you for the bug report. Could you please provide the create table statement on SQL Server. Thanks.
[23 Jan 2013 16:33] Robin Oaks 
The SQL Server 2008 R2 tinyint data typed field always holds values in the range of 0 to 255 (no negatives).  Is this what you are wondering about?

Create Table mytable( aTinyNumber tinyint)

I need the migration tool to put values between 0 and 255 in a MySql tinyint unsigned data type field (it throws 'out of range value' for a number > 127 which is max value in a signed tinyint) even though the MySql create table statement is correct. Or if I change the MySql create table statement to create the field as a smallint, the migration utility should copy those tinyint values into the smallint field (throws type mismatch).

After the migration tool creates the table, I can manually execute an insert statement that will add a value of >127.
[31 Jan 2013 21:37] MySQL Verification Team 
Thank you for the feedback.
[13 Jun 2013 0:51] Philip Olson 
Fixed as of the upcoming MySQL Workbench 6.0.2 beta release, and here's the changelog entry:

The Database Migration wizard would migrate unsigned tinyint Microsoft SQL
Server values, but would throw an exception for values exceeding 127 (the
maximum value for a signed tinyint).

Thank you for the bug report.