LAST_RUN

  • 28Views
  • Last Post 12 April 2018
  • Topic Is Solved
0
votes
Sean posted this 04 April 2018

Hello,

 

 I am using "LAST_RUN" as a condition to filter data to be imported and I found there's time time gap between actual value behind and what's show on "Date" column of task history,

I assume this is based on SKYVIA's host system instead of what's showing on the screen,

I am in Eastern Time zone and wondering if you can tell me what time zone this system is using internally?

I found the difference is 4 hours,

As attached screen shot I compare "CreateDate" column and "LAST_RUN" and it doen't update,

But if I change the time to 19 from 18 then it updates,

Sean

Attached Files

Order By: Standard | Newest | Votes
1
votes
Mariia Zaharova posted this 05 April 2018

 I assume this is based on SKYVIA's host system instead of what's showing on the screen,

 I am in Eastern Time zone and wondering if you can tell me what time zone this system is using internally?

I found the difference is 4 hours,

Date column in the Run History shows your actual time (in your case, Eastern Time).

Internally, Skyvia works with the UTC time zone. Please refer to: https://skyvia.com/resources/docs/index.html?importing_recently_added.htm (Workaround for Relational Databases)

It states:

Add columns for storing timestamps of creation time and/or last modification time to the database table you want to import data from yourself. The date and time in these columns must be in UTC.

 

In your Date column this value is shown (Skyvia)  - 04.04.2018 15:52

In your CreateDate column this value is shown (database) - 04.04.2018 18:59

 

The difference is 3 hours, however, must be 4 hours (in your case, Eastern Time). If you change CreateDate value to 04.04.2018 19:59 it will work as expected. Thus, we recommend you to check settings for the CreateDate column and corresponding trigger in your database.

  • Supported by
  • Sean
0
votes
Sean posted this 12 April 2018

This is resolved

Close