• SQL Timestamp ETL timezone problems a...
Why you must keep all your timestamp columns to UTC TimeZone ? It’s a very good problem to solve which I recently encountered in my project. So we were running an incremental job. It’s a daily job that loads data for the previous day from the source into the target table. There were no failures in the incremental job. The job was working fine. The Logic was correct. The missing data was because of TimeZone difference.
Source Start_Time & End_Time | Defined in US TimeZone
Target Start_Time & End_Time | Defined in EU TimeZone