Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Timestamp in Stats and Log Catcher

Hi,
In our current project, we have created a job that is executed from different servers located in different timezone. We have enabled Stats & Logs tracking on both files and databases.
All these job deployed on different severs however connect to the same database server. When the jobs are executed the database table contains date time stamps of the server from where the job is executed. Is it possible to store data in these tables with the timestamp of the database server instead? 
For example there is Server1 which has US-ET timezone and Server2 which has India timezone. And the database server DBServer has US-ET timezone. Now when the job is executed from Server2, the rows inserted in the database tables have India timezone date time stamps. Is it possible that when the job is executed from Server2, the data inserted in the Stats and Logs table have DBServer timestamps instead of Server2 timestamps?
Labels (2)
2 Replies
Anonymous
Not applicable
Author

Hi,
Is it possible that when the job is executed from Server2, the data inserted in the Stats and Logs table have DBServer timestamps instead of Server2 timestamps?

You can format your date type in tMap and then output them into your specified DB server.
tStatCatch-->tMap(format Server2 India timestamps into Server1 US-ET timezone  )-->t<DB>output
Best regards
Sabrina
Anonymous
Not applicable
Author

Hi,
Is it possible that when the job is executed from Server2, the data inserted in the Stats and Logs table have DBServer timestamps instead of Server2 timestamps?

You can format your date type in tMap and then output them into your specified DB server.
tStatCatch-->tMap(format Server2 India timestamps into Server1 US-ET timezone  )-->t<DB>output
Best regards
Sabrina

Hi,
This approach would work if the job is executed only from Server2 which has India timezone set. But if there are other servers, say Server3 which has Japan timezone and Server4 which has Singapore timezone which also execute the same job. Then as per the given approach, I will have make changes in the job for each server. Is there no other way to ensure that the data entering the Stats table has a uniform timezone?