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.

DB2

bigint

char

date

decimal

double

float

int

numeric

real

smallint

timestamp

varchar

Netezza

bigint

byteint

char(n) [1]

date

float(p)

int

nchar(n) [2]

numeric(p, s)

nvarchar(n) [2]

smallint

timestamp

varchar(n) [1]

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

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

Oracle

DATE

FLOAT (p)

NUMBER [ (p , s) ] [1]

TIMESTAMP

VARCHAR2(size BYTE)

1.

Precision is required when using NUMBER unless you have set the data source property Campaign > partitions > partition N > 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.

SQL Server

bigint

bit

char(n) [1]

datetime

decimal

float

int

nchar [2]

numeric

nvarchar [2]

real

smallint

text

tinyint

varchar(n) [1]

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

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

Teradata

bigint

byteint

char

date

decimal

float

int

numeric

smallint

timestamp

varchar