Skip to main content
Announcements
Global Transformation Awards submissions are open! SUBMIT YOUR STORY

Qlik Replicate: Explaining MS-CDC limitation

100% helpful (3/3)
cancel
Showing results for 
Search instead for 
Did you mean: 
Kent_Feng
Support

Qlik Replicate: Explaining MS-CDC limitation

Last Update:

Sep 9, 2024 7:34:52 AM

Updated By:

Sonja_Bauernfeind

Created date:

Sep 9, 2024 7:34:52 AM

Existing limitations of Microsoft SQL Server (MS-CDC) as a source for Qlik Replicate are documented in MS-CDC Limitations and considerations (help.qlik.com).

This article aims to provide additional context to some of the listed limitations.

Question: The AR_H_USER header column is not supported (link). Does it mean all AR_H_USER headers can not be used when using MS-CDC for replication?

Answer: AR_H_USER is a header, the limitation means this header is not available to be used in the target table when Using MS-CDC for replication.

Question: MS-CDC Change Tables with fixed size columns (including NCHAR and CHAR data), the sum of which exceeds 8060 bytes, are not supported. (link) Are varchar(max) columns included in this limitation?

Answer: Varchar(max) columns are not included in the 8060bytes limitation for fixed-size columns.

Question: RENAME TABLE will not be captured and Table-level DDLs are not supported. (link) Does it mean when Qlik Replicate receives DDL changes it will work for the first DDL statement and the task will stop and we have to rename the CT table manually?

Answer: All DDL changes including RENAME TABLE, alter column, etc. are not supported. The table will be suspended. The quickest workaround is to disable MS-CDC on the table, drop the CT table and re-enable MS-CDC. If you need to keep the ct table history, the other workaround is to manually fix ct table to reflect the DDL changes.

 

Related Content

 

Environment

  • Qlik Replicate
Labels (1)