Functionality of use_backend_local_time_in_ct_table_timestamp parameter

[qlik_admin_lm]

Can someone explain what the use_backend_local_time_in_ct_table_timestamp parameter actually does?  In running some tests I don't see any difference when it is present (value of true) in the task versus when it is not.  Is there documentation somewhere?

[john_wang]

Hello @qlik_admin_lm ,

In general the internal parameter are not documented, it should be used under Qlik Support guide.

Would you please share what's your source database type and how you set the parameter ? We'd like to confirm the behavior for you.

Thanks,

John.

[Heinvandenheuvel]

FWIW - Replicate internal parameters are typically named without underscores using CamelCase

The SAP source uses some _backend_ style naming

This may be a very SAP centric question.

Anyway, aren't the CT timestamps normally not in UTC? This parameter name suggests it would use the local time instead.

What timezones are the various components? sap-db, repl-source, rep-server, target,...

Hein. 

[qlik_admin_lm]

We are using it on a DB2 Z/Os source both in the logstream and child task.  Running tests, I don't see any difference running with it or without it.  Inherited this from another team and I'm not sure why the parameter is there so could use some help in what it's doing.  The parameter is set this way in the JSON of both the logstream and child task:

"use_backend_local_time_in_ct_table_timestamp": true

[DesmondWOO · Accepted solution]

Hi @qlik_admin_lm ,

I've found following information about this parameter:

If the source is either for DB2z or SQL Server, when turning on use_backend_local_time_in_ct_table_timestamp internal property for a task, the value of the commit timestamp column in the CT table and in the AR_H_COMMIT_TIMESTAMP will be the commit timestamp from the source backend as-is, without any manipulation.

Hope this helps.

Regards,
Desmond