Skip to main content

Actian Vector data types

The Actian Vector database for Qlik Replicate supports most Actian Vector data types. The following table shows the Actian Vector target data types that are supported when using Qlik Replicate and the default mapping from Qlik Replicate data types.

Information note

Actian Vector does not support applying changes to binary data types in Batch optimized apply mode. For more information on Batch optimized apply mode, see Change Processing Tuning.

For information on how to view the data type that is mapped from the source, see the section for the source database you are using. For additional information about Qlik Replicate data types, see Replicate data types.

Qlik Replicate and Actian Vector data types
Qlik ReplicateData Types Actian Vector Data Types

BOOLEAN

VARCHAR (length)

BYTES

If length is => 1 and =< 16000, then:

VARCHAR (Length in Bytes)

If length is => 16001 and =< 2147483647, then:

VARCHAR (32000)

DATE

ANSIDATE

TIME

TIME

DATETIME

TIMESTAMP

INT1

INTEGER1

INT2

SMALLINT

INT4

INTEGER

INT8

INTEGER8

NUMERIC

DECIMAL (p,s)

REAL4

FLOAT4

REAL8

FLOAT

STRING

If length is => 1 and =< 32000, then:

VARCHAR (Length)

If length is => 32001 and =< 2147483647, then:

VARCHAR (32000)

UINT1

SMALLINT

UINT2

INTEGER

UINT4

INTEGER8

UINT8

INTEGER8

WSTR

If length is => 1 and =< 16000, then:

NVARCHAR (Length)

If length is => 16001 and =< 2147483647, then:

NVARCHAR (16000)

BLOB

VARCHAR (16000)

NCLOB

NVARCHAR (16000)

Information note

The maximum LOB size in the Metadata tab cannot exceed 15 KB.

CLOB

In Batch optimized apply mode:

VARCHAR (32000)

Information note

In Batch optimized apply mode, the maximum LOB size in the Metadata tab cannot exceed 31 KB.

In Transactional apply mode:

VARCHAR (16000)

Information note

In Transactional apply mode, the maximum LOB size in the Metadata tab cannot exceed 31 KB.

For more information on Transactional apply and Batch optimized apply, see Change Processing Tuning.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!