Bug #24128 Property Auto_Increment not imported
Submitted: 9 Nov 2006 8:04 Modified: 10 Nov 2006 14:34
Reporter: Julien Gras Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.1.5 OS:Microsoft Windows (Windows 2000 Server)
Assigned to: CPU Architecture:Any
Tags: auto increment, auto_increment, sql server

[9 Nov 2006 8:04] Julien Gras
Description:
When i used MySQL migration toolkit to import my old data from my old server to my new one, it correctly re-import all data, but not the property "Auto_Increment" for my primary keys !!

How to repeat:
Creating a table with a primary key with auto_increment property on a server, and reimport this table to a new server
[9 Nov 2006 8:30] Julien Gras
I forgot to say that this import was made from a SQL Server and not from an another mySQL server !
[9 Nov 2006 15:43] MySQL Verification Team
Thank you for the bug report. I was unable to repeat, below how my test
case was migrated:

mysql> show create table tb1\G
*************************** 1. row ***************************
       Table: tb1
Create Table: CREATE TABLE `tb1` (
  `col1` int(10) NOT NULL auto_increment,
  `col2` char(10) default NULL,
  PRIMARY KEY  (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
1 row in set (0.05 sec)

mysql>
[10 Nov 2006 14:35] Julien Gras
In SQL Server

CREATE TABLE tb1 (
	col1 [numeric](18, 0) IDENTITY (1, 1) NOT NULL ,
	col2 [char] (20) COLLATE French_CI_AS NULL 
)

And after migration, in MySQL :

mysql> show create table tb1\G
*************************** 1. row ***************************
       Table: tb1
Create Table: CREATE TABLE `tb1` (
  `col1` decimal(18,0) NOT NULL,
  `col2` char(20) default NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1
1 row in set (0.00 sec)