Results 1 to 3 of 3

Thread: Column header__timestamp - where is timestamp originating from ?

  1. #1
    tille3787 is offline Junior Member
    Join Date
    Dec 2016
    Posts
    13
    Rep Power
    0

    Column header__timestamp - where is timestamp originating from ?

    Hi

    Here is 10 rows and 2 columns from a __CT table populated by a AQttunity Replicate Task

    header__timestamp LastModifiedDate
    2017-02-01 19:13:37.850000 2017-02-01 20:14:03.8330000
    2017-02-01 19:13:37.850000 2017-02-01 20:14:03.8500000
    2017-02-01 19:13:37.833000 2017-02-01 20:14:03.8200000
    2017-02-01 19:13:37.833000 2017-02-01 20:14:03.8330000
    2017-02-01 19:13:37.810000 2017-02-01 20:13:42.4300000
    2017-02-01 19:13:37.810000 2017-02-01 20:14:03.8200000
    2017-02-01 19:13:16.430000 2017-02-01 20:13:42.4300000
    2017-02-01 18:57:46.813000 2017-02-01 19:58:12.7770000
    2017-02-01 18:57:46.813000 2017-02-01 19:58:12.8170000
    2017-02-01 18:57:46.777000 2017-02-01 19:58:12.5530000

    LastModifiedDate is from the sourcetable, containing the timestamp of when an update to a row happened at the source

    i don't understand why there is one hour difference between header__timestamp and LastModifiedDate.

    where is header__timestamp getting the timestamp from ?

    if i check the two servers, the source and the target, the systemtime is the same, but apparently header__timestamp is not aligned with the system time or ...
    What is the reason for this ?

    regards Peter

  2. #2
    Hein is offline Senior Member
    Join Date
    Dec 2007
    Location
    Nashua, NH - USA.
    Posts
    165
    Rep Power
    13
    Where do you live? Don't answer that... let me guess: Germany?

    The difference may be 2 hours come April.

    Now do you know why there is one hour difference?

    The header_timestamp is in UTC (just like the ERROR_TIME in the target_apply_exceptions table, because the changes could be arriving from multiple database from multiple time zones. The only way to keep order is by going UTC (or localtime+TZ info)
    It's a bit of an inconvenience for casual interpretations, but easy enough to deal with in scripts/programs.
    And yes, I fall in the trap also every now and then.

    Hein

  3. #3
    tille3787 is offline Junior Member
    Join Date
    Dec 2016
    Posts
    13
    Rep Power
    0
    Where do you live? Don't answer that... let me guess: Germany?
    Close, just at north of Germany in Denmark :-)

    The header_timestamp is in UTC (just like the ERROR_TIME in the target_apply_exceptions table, because the changes could be arriving from multiple database from multiple time zones. The only way to keep order is by going UTC (or localtime+TZ info)
    It's a bit of an inconvenience for casual interpretations, but easy enough to deal with in scripts/programs.
    Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •