topic Re: Possible to include timezone information in AR_H_COMMIT_TIMESTAMP? in Qlik Replicate

Possible to include timezone information in AR_H_COMMIT_TIMESTAMP?

qlik_admin_lm — Thu, 18 Jul 2024 15:00:15 GMT

We are using the AR_H_COMMIT_TIMESTAMP variable in a global transformation that writes to a Snowflake target. The date in Snowflake is being created as a TIMESTAMP_LTZ column. However, we are finding that the timezone information is not being sent through by Qlik.

For example, the commit timestamp being generated on the Qlik server (running in America/New_York time) is 16:00:00. But when it is being written to Snowflake it is simply writing the 16:00:00 without the timezone information and therefore considers the 16:00:00 in the default timezone for the Snowflake account, in this case America/Los_Angeles time.

Is there a way within Qlik Replicate to send the timezone information along with the timestamp so that a TIMESTAMP_LTZ column within Snowflake will reflect the true time and time zone for when the data was committed?

Re: Possible to include timezone information in AR_H_COMMIT_TIMESTAMP?

john_wang — Thu, 18 Jul 2024 15:11:44 GMT

Hello @qlik_admin_lm ,

We have a discussion recently, see Override Snowflake TIMESTAMP_TYPE_MAPPING parameter via Qlik session.

Hope this helps.

John.

Re: Possible to include timezone information in AR_H_COMMIT_TIMESTAMP?

qlik_admin_lm — Thu, 18 Jul 2024 16:41:25 GMT

Hey John, that topic was about getting LTZ columns created in Snowflake from Qlik but now we have a question about how they are being populated. Is Qlik sending the time zone information through? It doesn't look like it is and when the Snowflake column is LTZ, it seems like it is just taking the date/time coming through and setting it according to the default time zone on for Snowflake.

We are wondering if there is a way within Qlik to send the actual timezone information through as part of the timestamp.