Microsoft has published SQL guidance for affected locations in British Columbia, Alberta and Manitoba that will stop changing their clocks on November 1, 2026. Applications using local dates and times should check their configured time zones before the change.

For SQL Server on Windows, Microsoft says the applicable Windows update supplies the time-zone definitions; a separate SQL Server update is not required. However, installing the Windows update does not rewrite explicit AT TIME ZONE expressions in application queries. Existing shared U.S.-and-Canada zone names may no longer represent the affected Canadian location correctly.

The guidance also covers SQL Server on Linux, Azure SQL Database and Managed Instance. Temporary substitute zones match future offsets, but they do not reproduce each province's complete historical rules. Avoid blanket changes to historical date conversions. Existing Managed Instances cannot change their instance-level time zone in place, and database/session overrides do not change SQL Agent schedules.

See Microsoft's October 14 SQL time-zone advisory for the location-specific mappings, exceptions and deployment guidance.