Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Destination Improvement: Fivetran unable to sync Datetime offset values from SQL Server source

Chaitanya User

Fivetran is bringing all Dates with Timezone, as UTC which means it loses the default timezone offset (like -0800 etc) and hence can not be CASTED into local time. This is very important since our reporting relies on this CASTED value. Please let us know how we can keep the source value timezone offset.

Here are our top priority columns for transformation to start with. You can either bring them as original value or as their transformed LocalTime in new columns (see example below). 
 
Table: landing.workforce_dbo.TECHNICIANTIMETRACKING
Columns: STARTTIME_DTO, ENDTIME_DTO
 
Sample data for how it is in our source and how it is landed in Fivetran staging. Added the CAST function to show you how we use them as LocalTime see _LT columns.
 
1. This is how data looks right now in Fivetran staging (see diff of data in 1 and 2).
2. This is how we would like to see them in Fivetran (either as original value (_DTO) or transformed to new columns Localtime (_LT) )
 

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Shilpa Madini User

    Thanks Chaitanya for opening this request. We would like this to be implemented not just for this table but for any table, column that has datetimeoffset fields.

    For each sql server table.column of datetimeoffset data type, fivetran sync should EITHER sync the data in its original format OR provide as additional column with local datetime with column names suffixed with _LT.

    Hope this clarifies.

    Thanks,

    Shilpa

  • Harsh Gandharv User

    Hi,

    Any updates on how to address this concern?
    I need to resolve this time offset issue in the data which flows into Snowflake via Fivetran.

  • Payal Patel User

    Hello team Fivetran,

    Any update on this request. we have use case where we are bringing telemetry data from vehicle movement and ignitions on -off and other data. we have this information coming from all Australia state,Tasmania and NZ which are all in different timezone. its difficult to add offset as seperate column in source so we need to rely on  position date time from source which is in local timezone of state. If data comes through UTC it is not possible to convert to local time if we dont have offset. Its not ideal to change source system to add timezone offset column as most of the Data integration tools should allow flexibiltiy to retain the source datetime in its native format. 

    Please suggest on timeline for this feature to available in GA.

     

    Thanks,

    Payal

  • ashish sharma User

    Hi, is there any update on this issue?

    We too need to retain the local time when data is synced from SQL Server to Snowflake. 

  • David Cross User

    Hi

    Any update on this feature request

    Removing the timezone from a date strips a vital piece of information. This seems like a basic piece of functionality that would be included in a product like Fivetran.

    Our use case is that we need to report to our Service centres regarding the volume of services that are provided out of business hours. They each have a contractual requirement to provide a proportion of services in non-business hours. Our head office is in a different time zone to many of our service centres and as such we must use the local time zone to accurately reflect this.