Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content

Supported data types

The following table shows the Microsoft Fabric Data Warehouse target data types that are supported when using Qlik Replicate and the default mapping from Qlik Replicate data types.

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.

Supported data types
Replicate data types Microsoft Fabric Data Warehouse data types

BOOL

BIT

BYTES

If length is 1-8000, then:

VARBINARY (Length in Bytes)

If length exceeds 8000, then:

VARBINARY (8000)

DATE

DATE

TIME

If scale is 0-6, then:

TIME (Scale)

If scale exceeds 6, then:

TIME (6)

TIMESTAMP

If scale is 0-6, then:

DATETIME2 (Scale)

If scale exceeds 6, then:

DATETIME2 (6)

INT1

SMALLINT

INT2

SMALLINT

INT4

INT

INT8

BIGINT

NUMERIC

DECIMAL (p,s)

REAL4

FLOAT(24)

REAL8

FLOAT(53)

STRING

If length in bytes is 1-8000, then:

VARCHAR (Length in Bytes)

If length in bytes exceeds 8000, then:

VARCHAR (8000)

UINT1

SMALLINT

UINT2

INT

UINT4

BIGINT

UINT8

DECIMAL (20,0)

WSTRING

If length in bytes is 1-8000, then:

VARCHAR (Length in Bytes)

If length in bytes exceeds 8000, then:

VARCHAR (8000)

BLOB

VARBINARY (8000)

Information note
  • VARBINARY (8000) applies to the entire record. So, for example, if the record contains two BLOB columns, their total size cannot exceed 8000 bytes.
  • When capturing changes, the maximum number of bytes that can be captured is 4000.

NCLOB

VARCHAR (8000)

CLOB

VARCHAR (8000)

Information noteFull LOB data types are not supported. For information on including Limited-size LOB data types in the replication, see the Metadata tab description in Customizing tasks .

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!