The following table identifies how SQL Anywhere and UltraLite remote data types are mapped to SAP HANA consolidated data types. For example, a column of type LONG VARBIT on the remote database should be type CLOB on the consolidated database.
SQL Anywhere or UltraLite data type | SAP HANA data type | Notes |
---|---|---|
BIT |
TINYINT |
|
TINYINT |
TINYINT |
|
SMALLINT |
SMALLINT |
|
UNSIGNED SMALLINT |
INTEGER |
|
INTEGER |
INTEGER |
|
UNSIGNED INTEGER |
BIGINT |
|
BIGINT |
BIGINT |
|
UNSIGNED BIGINT |
DECIMAL(20,0) |
|
DECIMAL(p,s) |
DECIMAL(p,s) |
|
NUMERIC(p,s) |
DECIMAL(p,s) |
|
FLOAT |
FLOAT |
The FLOAT data type should be avoided in remote databases with tables that download data from SAP HANA. |
REAL |
REAL |
The REAL data type should be avoided in remote databases with tables that download data from SAP HANA. |
DOUBLE |
DOUBLE |
|
SMALLMONEY |
DECIMAL(10,4) |
|
MONEY |
DECIMAL(19,4) |
|
DATE |
DATE |
|
TIME |
TIME |
SQL Anywhere and UltraLite fractional seconds cannot be preserved when using an SAP HANA TIME data type, which has no fractional seconds. To avoid problems, do not use fractional seconds. |
SMALLDATETIME |
TIMESTAMP |
|
DATETIME |
TIMESTAMP |
|
TIMESTAMP |
TIMESTAMP |
|
TIMESTAMP WITH TIME ZONE |
VARCHAR(34) |
There is no equivalent data type in SAP HANA so a TIMESTAMP WITH TIME ZONE column should be mapped to a VARCHAR(34) column. During upload, the MobiLink server converts the data to a string using the format 'yyyy-mm-dd hh:nn:ss.ssssss [+|-]hh:nn' and then applies it to the consolidated database. During download, the MobiLink server converts the data from a string to TIMESTAMP WITH TIME ZONE. Make sure the data in the consolidated database follows this format to avoid errors and synchronization failure. |
CHAR(n<=5000) |
VARCHAR(n) |
|
CHAR(n>5000) |
CLOB |
|
VARCHAR(n<=5000) |
VARCHAR(n) |
|
VARCHAR(n>5000) |
CLOB |
|
LONG VARCHAR |
CLOB |
|
NCHAR(n<=5000) |
NVARCHAR |
|
NCHAR(n>5000) |
NCLOB |
|
NVARCHAR(n<=5000) |
NVARCHAR(n) |
|
NVARCHAR(n>5000) |
NCLOB |
|
LONG NVARCHAR |
NCLOB |
|
BINARY(n<=5000) |
VARBINARY(n) |
|
BINARY(n>5000) |
BLOB |
|
VARBINARY(n<=5000) |
VARBINARY(n) |
|
VARBINARY(n>5000) |
BLOB |
|
LONG BINARY |
BLOB |
|
VARBIT(n<=5000) |
VARCHAR(n) |
|
VARBIT(n>5000) |
CLOB |
|
LONG VARBIT |
CLOB |
|
GUID |
VARCHAR(40) |
|
GEOMETRY |
Not supported. |
The following table identifies how SAP HANA consolidated data types are mapped to SQL Anywhere and UltraLite remote data types. For example, a column of type ALPHANUM(n) on the consolidated database should be type VARCHAR(n) on the remote database.
SAP HANA data type | SQL Anywhere or UltraLite data type | Notes |
---|---|---|
TINYINT |
TINYINT |
|
SMALLINT |
SMALLINT |
|
INTEGER |
INTEGER |
|
BIGINT |
BIGINT |
|
SMALLDECIMAL |
DECIMAL(p,s) |
In SQL Anywhere, DECIMAL p is between 1 and 127 and s is always less than or equal to p. In SAP HANA, p ranges from 1 to 16 and s ranges from -369 to 368. |
DECIMAL(p,s) |
DECIMAL(p,s) |
In SQL Anywhere, DECIMAL p is between 1 and 127 and s is always less than or equal to p. In SAP HANA, p ranges from 1 to 34 and s ranges from -6111 to 6176. |
FLOAT |
DOUBLE |
SAP HANA promotes FLOAT and REAL to DOUBLE. |
REAL |
DOUBLE |
SAP HANA promotes FLOAT and REAL to DOUBLE. |
DOUBLE |
DOUBLE |
|
DATE |
DATE |
|
TIME |
TIME |
SQL Anywhere and UltraLite fractional seconds cannot be preserved when using an SAP HANA TIME data type, which has no fractional seconds. To avoid problems, do not use fractional seconds. |
SECONDDATE |
TIMESTAMP |
SQL Anywhere and UltraLite fractional seconds cannot be preserved when using an SAP HANA SECONDDATE data type, which has no fractional seconds. To avoid problems, do not use fractional seconds. |
TIMESTAMP |
TIMESTAMP |
|
VARCHAR(n) |
VARCHAR(n) |
|
NVARCHAR(n) |
NVARCHAR(n) |
|
ALPHANUM(n) |
VARCHAR(n) |
|
VARBINARY(n) |
VARBINARY(n) |
|
CLOB |
LONG VARCHAR |
|
NCLOB |
LONG NVARCHAR |
|
BLOB |
LONG BINARY |
![]() |
Discuter à propos de cette page dans DocCommentXchange.
|
Copyright © 2013, SAP AG ou société affiliée SAP - SAP Sybase SQL Anywhere 16.0 |