I am currently using the Starter plan and would like to confirm whether the Relative Time filter is based only on the UTC timezone.
I can see that the report timezone setting only supports a specific list of data sources, and unfortunately my data source (Azure SQL Database) does not appear to be included. In this case, does that mean I am unable to configure the Relative Time filter to use our local timezone?
currently my datasource Date_ column is converting into AUS time zone:-
(TRY_CAST(TK.IssuedTimeUtc AS datetime2) AT TIME ZONE 'UTC' AT TIME ZONE 'AUS Eastern Standard Time') AS datetime2) AS Date_
but when i select Relative Time Filter options like Today, it follows the UTC. Is there any solution for my issue ?
Looking at the Azure docs, it doesn’t look like there’s an easy solution to this issue. Metabase usually implements ‘today’ filters as something like CAST(column AS date) = ‘2025-11-01’, so the times when ‘2025-11-01’ are, are up to the database.
Azure SQL Database appears to always use UTC. You can set the server timezone of Azure SQL Managed Instance only at create time, and there are caveats.
It doesn’t help that SQL Server was very late with adding the ‘timestamp with time zone’ type, and the implementation is still rather hacky. Compare that to PostgreSQL or Oracle where the type has been around forever.
SHOWER THOUGHT: It’s ugly, but if you always filter on dates (and not times), you could use “start” and “end” date filters and convert the values to local time in the query. This only works for SQL questions or models, but might be better than nothing.