Regarding delay in record retrieval from __ct table

Kankana_Das — Mon, 13 Jun 2022 12:52:30 GMT

hi Team,

We were doing an exercise to pull the records from __ct table( in target Postgres db) and pushing some change in the source system database (SQL Server) as some delay was reported by client team.

We observed that there is around 3~4 secs of the delay ( current timestamp in DB when the record first appears in __ct table) versus the header__timestamp/ $AR_H_TIMESTAMP values that are captured in __ct table.

Can you pls explain why do we see this delay , in spite of the $AR_H_TIMESTAMP value is captured earlier?

Pls see the screen capture for the resultset we got.

P.S. -we are capturing $AR_H_TIMESTAMP value in processed_timestamp column .

Re: Regarding delay in record retrieval from __ct table

Bill_Steinagle — Mon, 13 Jun 2022 20:43:44 GMT

Hello,

For more details and the usage of the $AR_H_TIMESTAMP and values please refer to the Qlik Replicate User Guide as shown in the 2021.11 Release User Guide link:

https://help.qlik.com/en-US/replicate/May2021/Content/Global_Common/Content/SharedEMReplicate/Customize%20Tasks/tasks_headColumns.htm

The timestamp is an approximate value.

Regards,

Qlik Support

topic Re: Regarding delay in record retrieval from __ct table in Qlik Replicate

Regarding delay in record retrieval from __ct table

Re: Regarding delay in record retrieval from __ct table