| DataGate® 16.0 for SQL Server Reference Guide
|
Native SQL Server Considerations
The following table details important considerations for Native SQL Server field interpretation when converting or communicating between DataGate® for IBM i, DataGate® for SQL Server, and the core DataGate® program.
|
Numerics |
Date/Time |
Char/Other |
|||
|
Float |
*Float(4) |
DateTime |
*Timestamp |
Bit |
*Boolean |
|
Real |
*Float (8) |
SmallDateTime |
*Timestamp |
Char |
*Char |
|
Int |
*Integer (4) |
|
|
VarChar |
*Char (VarLen) |
|
SmallInt |
*Integer (2) |
|
|
NChar |
*Unicode |
|
TinyInt |
*Integer (2) |
|
|
NVarChar |
*Unicode (VarLen) |
|
Decimal |
*Packed |
|
|
Binary |
*Hex |
|
BigInt |
*Zoned (19,0) |
|
|
VarBinary |
*Hex (VarLen) |
|
Money |
*Zoned (19,4) |
|
|
UniqueIdentifier |
*Hex (16) |
|
Numeric |
*Zoned |
|
|
|
|
|
SmallMoney |
*Zoned (9,4) |
|
|
|
|
The types Image, Text, and NText are not supported. Fields of these types are hidden from the file definition. You will be able to display the file definition in Database Manager but will not be able to open the file. To ensure future application compatibility, you should not use files containing these field types. Instead, you should create logical files naming the individual fields that your application will manipulate. That way, if in a future release the fields 'appear', your application will not break