MySQL Bugs: #14859: Importing tables from MS SQL ignores primary keys

Bug #14859	Importing tables from MS SQL ignores primary keys
Submitted:	11 Nov 2005 10:47	Modified:	11 Nov 2005 14:33
Reporter:	Miguelanxo Otero Salgueiro	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:		OS:
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
I'm using MySQL connector Version 3.51.12 to import a database from MS SQL to  
MySQL using the MS SQL Administration tool.

Everything seems right except the tables created in MySQL lack each and any PRIMARY KEY from the original (MS SQL) ones.

After having a chat on irc.freenode.org #mysql channel, I've been told to use the "migration tool" for this task, but also to report this as a bug in MySQL connector, so I'm just doing that.

How to repeat:
1.-Create a database in MS SQL with a table having a primary key

2.-Create a MySQL ODBC source using MySQL connector Version 3.51.12

3.-From the MS SQL administration tool, export the database created to a MySQL server using the odbc driver.

4.-Look at the table created in the new MySQL database and see it lacks the primary key constraint.

Versions used:

Exporting machine:

- MS SQL Enterprise Manager 8.0
- MS SQL Server Desktop engine, v.8.00.760 (SP3)
- Windows XP SP2 (x86)

Importing machine:

- MySQL connector v.3.51.12
- MySQL Server v.4.0 (ubuntu package v.4.0.24)
- Ubuntu Linux (Breezy Badger, x86)

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

The MyODBC driver just execute the create table definition which
receives from the adminsitration tool. Please use the Migration Tool for.