Joel Buhr
asked on
Convert MS Sql Field Types and Sizes to MYSQL Ideal Field Types and Sizes
I am running to something that I am sure might be straight forward for some but for some reason its just not clicking. So I thought I would put this out there for the community to help.
The MySQL db that I am putting this in incase it helps, using MyISAM, and the Character Set: Latin1 and Collation Latin1
The MS Sql I converted Strings to CHAR and V_Strings to VARCHAR. The others though I am just wanting to make sure.
Here are the fields in question.
TYPE LENGTH
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Date 10
Date 10
Date 10
DATE 10
DATE 10
DateTime 19
Double 8
Double 8
Int16 2
Int32 4
Int32 4
Int32 11
Here is what I was doing.
Length
Byte = TinyInt 1
Int64 = BigInt 8
Int32 = Int 11
Int16 = SmallInt 2
Is this correct? Is there a different recommendation for data type and length?
The MySQL db that I am putting this in incase it helps, using MyISAM, and the Character Set: Latin1 and Collation Latin1
The MS Sql I converted Strings to CHAR and V_Strings to VARCHAR. The others though I am just wanting to make sure.
Here are the fields in question.
TYPE LENGTH
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Byte 1
Date 10
Date 10
Date 10
DATE 10
DATE 10
DateTime 19
Double 8
Double 8
Int16 2
Int32 4
Int32 4
Int32 11
Here is what I was doing.
Length
Byte = TinyInt 1
Int64 = BigInt 8
Int32 = Int 11
Int16 = SmallInt 2
Is this correct? Is there a different recommendation for data type and length?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for the quick response.
https://dev.mysql.com/doc/workbench/en/wb-migration-database-mssql-typemapping.html
The comments about subtle differences are very helpful.
Bye, Olaf.