Bug #48038 migration toolkit fails to generate valid script for mssql field
Submitted: 14 Oct 2009 10:27 Modified: 15 Oct 2009 9:08
Reporter: gus legge Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.1.17 OS:Windows
Assigned to: CPU Architecture:Any

[14 Oct 2009 10:27] gus legge 
Description:
The migration toolkit generate incorrect sql for the MS sql field bit default(0)

How to repeat:
MS SQL Statement
----------------

CREATE TABLE [dbo].[Town](
	[TownCode] [int] IDENTITY(1,1) NOT NULL,
	[CountyCode] [int] NOT NULL,
	[TownName] [varchar](50) NOT NULL,
	[IsAreaOrStreet] [bit] NOT NULL CONSTRAINT [DF_Town_IsAreaOrStreet]  DEFAULT ((0)),
	[RelayCode] [nvarchar](50) NULL,
	[RelayOnly] [bit] NOT NULL CONSTRAINT [DF_Town_RelayOnly]  DEFAULT ((0)),
	[IsOther] [bit] NULL,
 CONSTRAINT [PK_Town] PRIMARY KEY CLUSTERED 
(
	[TownCode] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]

Generate MY SQL statement
-------------------------

DROP TABLE IF EXISTS `RiskDB_dbo`.`Town`;
CREATE TABLE `RiskDB_dbo`.`Town` (
  `TownCode` INT(10) NOT NULL AUTO_INCREMENT,
  `CountyCode` INT(10) NOT NULL,
  `TownName` VARCHAR(50) NOT NULL,
  `IsAreaOrStreet` TINYINT NOT NULL DEFAULT (0),
   `IsOther` TINYINT NULL,
  PRIMARY KEY (`TownCode`),
  CONSTRAINT `FK_Town_County` FOREIGN KEY `FK_Town_County` (`CountyCode`)
    REFERENCES `RiskDB_dbo`.`County` (`CountyCode`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION
)
ENGINE = INNODB;
[14 Oct 2009 10:51] Valeriy Kravchuk 
Thank you for the problem report. The statement generated is indeed wrong. What exact version of MT you had used?
[14 Oct 2009 11:57] gus legge 
Hi,

Version is Migration Toolki 1.1.14 running on windows xp
[14 Oct 2009 13:13] Valeriy Kravchuk 
Please, try to repeat with a newer version, 1.1.17, and inform about the results.
[14 Oct 2009 14:27] gus legge 
just verified the same error occurs in 1.1.17
[14 Oct 2009 17:04] MySQL Verification Team 
I am getting the below error while processing:

The schema could not be reverse engineered (error: 0).
ReverseEngineeringMssql.reverseEngineer :I/O Error: Connection reset
Details:
[15 Oct 2009 9:08] Susanne Ebrecht 
This is a duplicate of bug #26308