Hi,
I have an Azure SQL Server database with many tables and queries that use DateTime fields where the data is stored in UTC. However Metabase will only present the data or filter on UTC (even though the MB configuration states my timezone).
The warning i get is “the query was run in UTC rather than [timezone] due to database or driver constraints”.
Workarounds: I could customise and create specific views for all tables to cater for Metabase (translating all timezones to a fix timezone). Noting I present data using the local timezone for other connected apps.
Downside: for creating the views as a workaround is “questions” and much of the standard functionality of Metabase won’t be correct. You’d need a DBA to create customer views for all data.
And the view would only show a single timezone rather than cater for the user’s view timezone dynamically.
Preference: There is a SQL Server connection configuration in Metabase where you set the default timezone for date data for the connection globally. Metabase then can assume all data in the database is in UTC and translate to the local timezone (or it automatically shims the queries).
NB: I’m using Metabase v0.56.9 self-hosted on Docker using postgres.