Bug #72060 Don´t copy milliseconds from SQLServer to MySQL5.6 having a datetime(3)
Submitted: 17 Mar 2014 12:04 Modified: 12 Sep 2014 16:55
Reporter: Javi Jurado Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S3 (Non-critical)
Version:6.2.1 OS:Windows (2012)
Assigned to: CPU Architecture:Any
Tags: datetime, milliseconds, mysql5.6, SQLServer

[17 Mar 2014 12:04] Javi Jurado 
Description:
I'm trying to copy a table with a column type datetime with milliseconds presicion, from MSSQLServer 2008 to MySQL 5.6, but in the target DB the milliseconds are filled with .000

 

How to repeat:
Copying a datetime column with milliseconds precision from SqlServer 2008 to MySQL 5.6 (column type in MySQL 5.6 is datetime(3)). Runing Workbench from Windows 2012
[17 Mar 2014 15:36] Milosz Bodzek 
Confirm, i can repeat.
[15 Apr 2014 12:33] Milosz Bodzek 
Posted by developer:
 
Fixed
[30 Apr 2014 9:45] Javi Jurado 
I'm trying to copy with 6.1.4.11773 BUILD 1454 Workbench version, and the problem continues.
What is the fixed version?
[2 May 2014 16:59] Johannes Taxacher 
Posted by developer:
 
first, the target column is only created as "DATETIME" (which doesn't store millisecond values) but even when manually correcting the target table creation the values copied don't include the millisecond values stored in the source MS SQL Server tables - so i guess the copytable-helper needs to be adjusted for that too
[2 May 2014 17:28] Johannes Taxacher 
Posted by developer:
 
disregard my last comment ... i tested in build 6.1.6 while the fix only went into 6.2.1.
[6 May 2014 8:05] Javi Jurado 
Is the 6.2.1 version available for download?, On the Mysql workbench website is the 6.1 version.  http://www.mysql.com/products/workbench/
[26 Aug 2014 5:41] Philip Olson 
Fixed as of the upcoming MySQL Workbench 6.2.2 release, and here's the changelog entry:

When migrating from Microsoft SQL Server 2008 to MySQL 5.6+, copying a
table with the column type DATETIME using milliseconds precision would
only fill the target entry milliseconds as .000.

Thank you for the bug report.
[4 Sep 2014 8:58] Javi Jurado 
Now the program copies the milliseconds but with an error. When the milliseconds are less than 100, p.e. .067 , workbench copies .670
[12 Sep 2014 16:55] Milosz Bodzek 
Issue with bad import when the milliseconds are less than 100 fixed in 6.2.2.2306