I am using an SQL server which has the timezone set to IST. But when I am going through the data in metabase, the time column shows the time in UTC instead of IST.
My Report timezone in localization is set to "Asia/Kolkata" and the diagnostic info in troubleshooting also has the user.timezone set to "Asia/Kolkata".
The server that the metabase instance is running on has the same timezone. The timezone in the sqlserver is also the same. The column which is showing this issue has field type as "No field type" and data type set as "type/Datetime"
If you are an Enterprise customer or trying a trial, then please use the support email.
If you just want the free open source edition, then download the correct JAR file. https://github.com/metabase/metabase/releases
Since the computer on which my sql server is running has the correct timezone set, can you please let me know as to why metabase is not able to correctly show the time value?
@PD98 Do this query in Metabase on the MSSQL db select current_timestamp; - that's not the same as a datetime column.
I cannot tell you how complicated timezones are, but it quickly becomes extremely complex. If you think there's an issue in Metabase, which you don't find in one of the many timezone issues, then please open a new issue with exact information on how to reproduce (otherwise it will never get fixed if it cannot be reproduced). https://github.com/metabase/metabase/issues?q=is%3Aopen+is%3Aissue+label%3AMisc%2FTimezones
Anyway, like I already wrote, we are working on making it possible to define timezones much more granular in upcoming 0.42, so your problem would likely be fixed there.