Possible timezone inconsistency between SQL Server log-based and SQL Server (MS-CDC) header__timestamp in Replicate 2024.11.0.177

[korsikov]

Hello Qlik community,

We have two Qlik Replicate tasks running on the same Replicate Server and writing Change Tables to the same Microsoft SQL Server target.

Environment:
- Qlik Replicate: November 2024, build 2024.11.0.177
- Target SQL Server versions: 15.0.4470.1 

- Source SQL Server and 16.0.1180.1 Endpoint A  and 16.0.1180.1 for Endpoint B

- All source servers, Replicate Server, and target SQL Server are configured UTC+3

Tasks:
- Endpoint A: Microsoft SQL Server source using MS-Replication / log-based capture
- Endpoint B: Microsoft SQL Server (MS-CDC) source
- Both tasks use global transformation for soft delete capturing:
OperationDateTime DATETIME(6) = datetime('now')

Observed example :
- Log-based source:
header__timestamp = 2026-07-23 16:23:00.304
OperationDateTime = 2026-07-23 16:23:01
header__change_seq starts with 2026072316230032

- MS-CDC source:
header__timestamp = 2026-07-23 19:22:55.407 <===localtime!!!
OperationDateTime = 2026-07-23 16:23:14
header__change_seq starts with 2026072316230086

Validation:
- For MS-CDC, header__timestamp matches sys.fn_cdc_map_lsn_to_time(__$start_lsn)

Question:
Public Qlik documentation appears inconsistent:
- Change Tables article says header__timestamp is UTC timestamp of the original change  https://help.qlik.com/en-US/replicate/May2026/Content/Replicate/Main/Change%20Tables/read_change_tab...

- We do not see any documented endpoint-specific timezone difference between SQL Server log-based and SQL Server (MS-CDC)

Question's:
 Expected timezone semantics of header__timestamp for each endpoint type?
 Recommended supported header/column for Qlik Compose Type 2 FROM/TO dates across mixed SQL Server source endpoint types

Best regards

[korsikov · Accepted solution]

Solution  set customHeaderForTs = False in Endpoint -  Internal Parameters

and restart Replicatation task.
now you see header__timestamp  in UTC