Supported data types for user tables

This topic lists the data types that Campaign supports for user tables created in each supported database. Any other data types not listed here are unsupported. Before mapping user tables in Campaign , ensure that your tables use only supported data types.

A column of datatype DATE, DATETIME, or TIMESTAMP of a table, when mapped in an IBM® Campaign flowchart, appears as type TEXT with the format of the DATE, DATETIME, or TIMESTAMP stored in brackets, such as [DELIM_D_M_Y] or [DT_DELIM_D_M_Y]. Although its data type in table mapping in the flowchart shows as TEXT, the application knows the format and handles it accordingly. Do not map columns of these three data types or any of the date- or time-related data types as an Audience ID column to a TEXT audience level. Mapping the date-related column as TEXT audience level is not supported.

DB2®

Netezza®

char(n) [1]

nchar(n) [2]

nvarchar(n) [2]

varchar(n) [1]

Not supported when used in the same table with nchar or nvarchar.

Not supported when used in the same table with char or varchar.

Oracle

DATE

FLOAT (p)

NUMBER [ (p , s) ] [1]

TIMESTAMP

VARCHAR2(size BYTE)

Precision is required when using NUMBER unless you have set the data source property Campaign > partitions > partitionN > dataSources > [dataSourceName] > UseSQLToRetrieveSchema to TRUE. If you do not specify a precision and do not set that data source property, Campaign assumes it can store the values in a data type that preserves 15 digits of precision. This can be problematic because, if the field holds values whose precision exceeds 15 digits, precision will be lost when the value is brought into Campaign.

char(n) [1]

nchar [2]

nvarchar [2]