Time zones and UTC handling

Concepts: sqlTimezones

Time zones are one of the most error-prone areas in data engineering. A timestamp without timezone context is ambiguous. Is "2025-03-15 14:00:00" in UTC? Eastern Time? The server's timezone? Incorrect assumptions lead to data shifted by hours, causing wrong aggregations and confused stakeholders. Timezone Best Practices Following these guidelines helps avoid timezone-related bugs in global applications. Always use full IANA timezone names like America/New_York rather than abbreviations like EST, which are ambiguous and do not handle daylight saving transitions. Storing timestamps in UTC and converting to local time at display is the most reliable strategy for global applications. AT TIME ZONE adjusts both the displayed value and the timezone offset, ensuring correct representation across a