Fabric pipeline copy activity converts time to UTC

[TomDA]

I am using a pipeline copy activity to copy a table from an on-premises SQL Server database to a Fabric lakehouse, and all datetime, datetime2 and datetimeoffset columns appear to be automatially converting to UTC, from the local timezone. I don't want timestamps stored in UTC as all reporting is in local time. Is there a way to disable this?

[TWorku]

I had the same issue. Updating the Gateway to latest version solved the problem. Thank You community 

[Rk_1411]

Any update on this?

[TomDA]

Hi @Rk_1411 , no this was not resolved by MS support, they only suggested a workaround which was to convert the dates after loading, using SQL. They also recognised that it is not expected behaviour and does not occur in all regions

[Rk_1411 · Accepted solution]

It is resolved for me. I updated the On pren data gateway to the latest version July 2024 and that seems to fix the issue.

[TomDA]

@Rk_1411 , thanks yes that worked for me also

[ChiaraMiani]

Hi! Can you please give me details on the gateway you've installed?
We updated it but we still have the issue with the dates.

Thanks!

[mkjit256]

Any updates? I did upgrade the datagateway to the latest version, and i am still haivng the same issue. My source is an Oracle DB with a time zone America/New York and yet my dates are converted to UTC. 

[TomDA]

Thanks. Case 2405090030001741

[v-cboorla-msft]

Hi @TomDA 

Thanks for sharing the details.

[v-cboorla-msft]

Hi @TomDA 

Thanks for using Microsoft Fabric Community.

At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.
Appreciate your patience.

Thanks.

[v-cboorla-msft]

Hi @TomDA 

Apologies for the inconvenience.

Please reach out to our support team to gain deeper insights and explore potential solutions. It's highly recommended that you reach out to our support team. Their expertise will be invaluable in suggesting the most appropriate approach.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thank you.

[MisterSmith]

We are experencing the same issue, do you know if this is on the Fabric development team's radar to fix?  As it is causing us an overhead to rectify.