Datatype Mapping for the SAP ASE Output Adapter

Event Stream Processor datatypes map to SAP ASE datatypes.

Event Stream Processor does not have datatypes equivalent to these SAP ASE datatypes:

tinyint
smallint
unsigned smallint
unsigned int
unsigned bigint
smallmoney

To use existing SAP ASE schemas containing these datatypes, SAP supports mapping of integer, long, money and money(1-15) Event Stream Processor datatypes to those SAP ASE datatypes.

During message flow, the adapter verifies that incoming values can fit into the specified SAP ASE columns without losing precision, and rejects the rows if they cannot. Any SAP ASE column datatypes that are marked with an asterisk have data dependent limitations on the mapping, and only these mappings are verified for each record flowing through the adapter. Due to the performance impact of runtime checks on each record, SAP recommends you do not use these mappings unless you cannot make changes to existing schemas.

Event Stream Processor Datatypes	SAP ASE Datatypes	Notes
`bigdatetime`	`time, bigtime, bigdatetime, datetime`
`binary`	`binary(n), varbinary(n)`
`boolean`	`bit, tinyint, smallint, int, bigint, unsigned smallint, unsigned int, unsigned bigint*, varchar(5)`	For `boolean` values that map to `varchar(5)` columns, the adapter inserts the text "true" or "false" into the database table. For boolean values that map to various integer database columns, the adapter inserts values 1 or 0.
`seconddate`	`date, smalldatetime, datetime, bigdatetime`
`decimal`	`decimal, numeric`	ESP performs runtime checks to ensure the whole-number portion of your decimal fits into the database column. However, ESP does not ensuer the fractional portion fits into the database column.
`float`	`double precision, numeric, decimal`	There is no required precision or scale for `float` to `numeric` or `decimal` mapping during adapter initialization. However, during message flow, any rows that generate an error occur while data is converting from Event Stream Processor `float` to SAP ASE `numeric` or `decimal` is rejected. This generally occurs due to insufficient precision of the target `numeric` and `decimal` datatype.
`integer`	`tinyint, smallint, unsigned smallint*, int, bigint, money, numeric` and `decimal` datatypes with precision minus scale equals or is greater than 10
`interval`	`bigint`
`long`	`unsigned int, bigint, unsigned bigint, numeric` and `decimal` datatypes with precision minus scale equals or is greater than 19
`money`	`smallmoney, money, numeric` and `decimal*` datatypes with scale >= 4
`money(n)`	`numeric(p,s)` and `decimal(p,s)` datatypes with scale >= n
`string`	`char(n), varchar(n)`	If the destination column is not large enough to store the `string` value, the value is truncated to fit the column and a warning is written in the ESP Server logs.
`time`	`time, bigdatetime`	When the ESP `time` value is mapped to SAP ASE `bigdatetime` value, the date portion is set to January1, 1970 (the UNIX epoch).
`msdate`	`bigdatetime`, `datetime`