Whenever we extract data using a database query SQL server any datetime from our source system is in local time when it lands in snowflake it assumes it is UTC time and adds 11 hours to it.
Anyone had this issue before?
Whenever we extract data using a database query SQL server any datetime from our source system is in local time when it lands in snowflake it assumes it is UTC time and adds 11 hours to it.
Anyone had this issue before?
We have seen this before. I can't remember the details, but I think it was a combination of SQL Server version and JDBC driver type and version which caused this.
There are actually two different JDBC drivers for SQL Server - the "official" Microsoft driver and and open JDTS driver. You could try the one which you are currently not using and see if it makes a difference. Even if that does not solve the issue for you, you should get an idea why this is happening.
Can you check your Snowflake settings for timezone? If they are not in your local timezone , your timestamp values might be converted to UTC.
If that is the case, get your ACCOUNTADMIN to change them to your local timezone.
Thank you for your answer.
I have found the issue we did check the timezone in snowflake but the issue ending up being the server time that the Matillion instance was running on was set to UTC time.
Once I got this updated and Matillion was restarted the issue is resolved.
This is in our DEV environment as we haven't moved anything to PROD yet still in development.