{"id":7808,"date":"2026-10-14T22:21:10","date_gmt":"2026-10-15T05:21:10","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/azure-sql\/?p=7808"},"modified":"2026-11-04T16:39:15","modified_gmt":"2026-11-05T00:39:15","slug":"canadas-2026-time-zone-updates-guidance-for-microsoft-sql","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azure-sql\/canadas-2026-time-zone-updates-guidance-for-microsoft-sql\/","title":{"rendered":"Canada\u2019s 2026 time zone updates: guidance for Microsoft SQL"},"content":{"rendered":"<p><span data-contrast=\"auto\">Affected locations in British Columbia, Alberta, and Manitoba will <\/span><b><span data-contrast=\"auto\">not turn their clocks back at 02:00 local time on November 1, 2026<\/span><\/b><span data-contrast=\"auto\">. They will remain at UTC\u221207:00, UTC\u221206:00, and UTC\u221205:00, respectively.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Microsoft\u2019s interim guidance for <\/span><a href=\"https:\/\/techcommunity.microsoft.com\/blog\/dstblog\/interim-guidance-for-british-columbia-time-zone-changes-2026\/4544988\"><span data-contrast=\"none\">British Columbia<\/span><\/a><span data-contrast=\"auto\">, <\/span><a href=\"https:\/\/techcommunity.microsoft.com\/blog\/dstblog\/interim-guidance-for-alberta-time-zone-changes-2026\/4545015\"><span data-contrast=\"none\">Alberta<\/span><\/a><span data-contrast=\"auto\">, and <\/span><a href=\"https:\/\/techcommunity.microsoft.com\/blog\/dstblog\/interim-guidance-for-manitoba-permanent-dst-2026\/4562488\"><span data-contrast=\"none\">Manitoba<\/span><\/a><span data-contrast=\"auto\"> describes the new Windows time zones and temporary workarounds.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><b><span data-contrast=\"auto\">SQL Server on Windows requires the applicable Windows update\u2014not a separate SQL Server product update.<\/span><\/b><span data-contrast=\"auto\"> For SQL Server on Linux, Azure SQL Database, and Azure SQL Managed Instance, the following guidance applies when the new regional time zones are not yet available in your deployment.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<h2>Known issue with new Canadian time zones<\/h2>\n<p>All SQL products are affected by a known .NET <code>TimeZoneInfo<\/code> issue with the new Canadian Windows time zones for <strong>Manitoba, Alberta, and British Columbia<\/strong>. For one hour at the <strong>2026\/2027 year boundary<\/strong>, the previous year\u2019s standard UTC offset may be applied, resulting in an incorrect local time or UTC offset. Customers who require time zone conversions during the affected period should use the <strong>interim time zone guidance<\/strong> until a SQL fix is available. Customers should apply the SQL update containing the fix when it becomes available. The issue is tracked in <strong>dotnet\/runtime #136894<\/strong>.<\/p>\n<h2><b><span data-contrast=\"none\">Interim guidance when the new time zone is unavailable<\/span><\/b><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\n<p><span data-contrast=\"auto\">This table adapts the Windows interim guidance for SQL. Use the interim identifiers for explicit SQL conversions, SQL Database or eligible SQL Managed Instance database\/session settings, mapped Linux configuration, or <\/span><b><span data-contrast=\"auto\">new SQL Managed Instances<\/span><\/b><span data-contrast=\"auto\">. The instance-level time zone setting cannot be modified for\u00a0an existing\u00a0SQL\u00a0Managed Instance.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;201341983&quot;:0,&quot;335551550&quot;:1,&quot;335551620&quot;:1,&quot;335559685&quot;:0,&quot;335559737&quot;:0,&quot;335559738&quot;:240,&quot;335559739&quot;:240,&quot;335559740&quot;:278}\">\u00a0<\/span><\/p>\n<table style=\"width: 100%\" data-tablestyle=\"MsoTableGrid\" data-tablelook=\"1696\">\n<tbody>\n<tr>\n<td style=\"width: 24.142%\" data-celllook=\"69633\"><b><span data-contrast=\"auto\">Affected area<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td style=\"width: 15.858%\" data-celllook=\"65537\"><b><span data-contrast=\"auto\">Existing SQL time zone<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"65537\"><b><span data-contrast=\"auto\">Interim SQL time zone<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.0118%\" data-celllook=\"65537\"><b><span data-contrast=\"auto\">Required offset from November 1<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"65553\"><b><span data-contrast=\"auto\">Final regional time zone<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 24.142%\" data-celllook=\"4096\"><span data-contrast=\"auto\">Most of British Columbia<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 15.858%\" data-celllook=\"0\"><span data-contrast=\"auto\">Pacific Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"0\"><span data-contrast=\"auto\">Yukon Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.0118%\" data-celllook=\"0\"><span data-contrast=\"auto\">UTC\u221207:00<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"16\"><span data-contrast=\"auto\">British Columbia Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 24.142%\" data-celllook=\"4096\"><span data-contrast=\"auto\">Alberta and locations covered by its guidance*<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 15.858%\" data-celllook=\"0\"><span data-contrast=\"auto\">Mountain Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"0\"><span data-contrast=\"auto\">Canada Central Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.0118%\" data-celllook=\"0\"><span data-contrast=\"auto\">UTC\u221206:00<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"16\"><span data-contrast=\"auto\">Alberta Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 24.142%\" data-celllook=\"4352\"><span data-contrast=\"auto\">Manitoba<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 15.858%\" data-celllook=\"256\"><span data-contrast=\"auto\">Central Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"256\"><span data-contrast=\"auto\">Eastern Standard Time (Mexico)<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.0118%\" data-celllook=\"256\"><span data-contrast=\"auto\">UTC\u221205:00<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 18.1065%\" data-celllook=\"272\"><span data-contrast=\"auto\">Manitoba Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><i><span data-contrast=\"auto\">*The Alberta guidance also covers southeastern BC locations aligning with Alberta and affected Northwest Territories locations, including Yellowknife and Inuvik. Do not apply the first row to all of BC.<\/span><\/i><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">For Manitoba, the Windows workaround uses ordinary <\/span><span data-contrast=\"auto\">Eastern Standard Time<\/span> <b><span data-contrast=\"auto\">with automatic DST adjustments disabled<\/span><\/b><span data-contrast=\"auto\">. SQL\u2019s <\/span><span data-contrast=\"auto\">AT TIME ZONE<\/span><span data-contrast=\"auto\"> does not provide the DST adjustment switch. Instead, <\/span><span data-contrast=\"auto\">Eastern Standard Time (Mexico)<\/span><span data-contrast=\"auto\"> supplies UTC\u221205:00 without seasonal changes under its current rules. Ordinary <\/span><span data-contrast=\"auto\">Eastern Standard Time<\/span><span data-contrast=\"auto\"> returns to UTC\u221204:00 in summer.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;201341983&quot;:0,&quot;335551550&quot;:1,&quot;335551620&quot;:1,&quot;335559685&quot;:0,&quot;335559737&quot;:0,&quot;335559738&quot;:240,&quot;335559739&quot;:240,&quot;335559740&quot;:278}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Confirm that the selected identifier is available in <\/span><span data-contrast=\"auto\">sys.time_zone_info<\/span><span data-contrast=\"auto\"> on the target deployment. These substitutes match the required current and future offsets, <\/span><b><span data-contrast=\"auto\">not the provinces\u2019 complete historical rules<\/span><\/b><span data-contrast=\"auto\">. Do not blanket-replace historical conversions. Move to the regional definition when supported, using the appropriate product-specific method.<\/span><\/p>\n<p>Below are the interim time zone values with the name or description property along with the UTC offset. You would typically see this name value in OS time zone selector or Azure Portal UI.<\/p>\n<table style=\"border-collapse: collapse;width: 100%;height: 96px\">\n<tbody>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\"><b><span data-contrast=\"auto\">Interim SQL time zone<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td style=\"width: 50%;height: 24px\"><b><span data-contrast=\"auto\">Time zone name displayed in the UI<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\"><span data-contrast=\"auto\">Yukon Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 50%;height: 24px\">(UTC-07:00) Yukon<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\"><span data-contrast=\"auto\">Canada Central Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 50%;height: 24px\">(UTC-06:00) Saskatchewan<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\">Eastern Standard Time (Mexico)<\/td>\n<td style=\"width: 50%;height: 24px\">(UTC-05:00) Chetumal<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0Below are the final time values with the name property along with the UTC offset.<\/span><\/p>\n<table style=\"border-collapse: collapse;width: 100%;height: 96px\">\n<tbody>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\"><b><span data-contrast=\"auto\">Interim SQL time zone<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td style=\"width: 50%;height: 24px\"><b><span data-contrast=\"auto\">Time zone name displayed in the UI<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\"><span data-contrast=\"auto\">British Columbia Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 50%;height: 24px\">(UTC-07:00) Pacific Time (British Columbia)<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\"><span data-contrast=\"auto\">Alberta Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 50%;height: 24px\">(UTC-06:00) Mountain Time (Alberta)<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 50%;height: 24px\">Manitoba Standard Time<\/td>\n<td style=\"width: 50%;height: 24px\">(UTC-05:00) Manitoba<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><b><span data-contrast=\"none\">SQL Server on Windows<\/span><\/b><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\n<p><span data-contrast=\"auto\">SQL Server reads installed Windows time zones from the OS registry, as documented for <\/span><a href=\"https:\/\/learn.microsoft.com\/en-us\/sql\/relational-databases\/system-catalog-views\/sys-time-zone-info-transact-sql\"><span data-contrast=\"none\">sys.time_zone_info<\/span><\/a><span data-contrast=\"auto\">.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Install the applicable Windows update. When the server\u2019s local time must follow the affected region, select the new regional zone under <\/span><b><span data-contrast=\"auto\">Settings &gt; Time &amp; language &gt; Date &amp; time<\/span><\/b><span data-contrast=\"auto\">, following the provincial guidance linked above.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Also update explicit <\/span><span data-contrast=\"auto\">AT TIME ZONE<\/span><span data-contrast=\"auto\"> references where appropriate. Installing the update does not rewrite application SQL or make the existing shared US-and-Canada identifier equivalent to the new province-specific definition.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<h2><b><span data-contrast=\"none\">SQL Server on Linux<\/span><\/b><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\n<p><span data-contrast=\"auto\">Follow <\/span><a href=\"https:\/\/learn.microsoft.com\/en-us\/sql\/linux\/configure\/time-zone?view=sql-server-ver17\"><span data-contrast=\"none\">Configure the time zone for SQL Server on Linux<\/span><\/a> for SQL Server 2022 or later<span data-contrast=\"auto\">. SQL Server on Linux map the Linux\/IANA time zone to a Windows identifier used internally by T-SQL.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;201341983&quot;:0,&quot;335551550&quot;:1,&quot;335551620&quot;:1,&quot;335559685&quot;:0,&quot;335559737&quot;:0,&quot;335559738&quot;:240,&quot;335559739&quot;:240,&quot;335559740&quot;:278}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">The documented mappings for the interim choices are:<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<table data-tablestyle=\"MsoTableGrid\" data-tablelook=\"1696\">\n<tbody>\n<tr>\n<td data-celllook=\"69633\"><b><span data-contrast=\"auto\">Affected region<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td data-celllook=\"65537\"><b><span data-contrast=\"auto\">Linux\/IANA identifier<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td data-celllook=\"65553\"><b><span data-contrast=\"auto\">SQL time zone identifier<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td data-celllook=\"4096\"><span data-contrast=\"auto\">Most of BC<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"0\"><span data-contrast=\"auto\">America\/Whitehorse<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"16\"><span data-contrast=\"auto\">Yukon Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td data-celllook=\"4096\"><span data-contrast=\"auto\">Alberta and aligned locations<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"0\"><span data-contrast=\"auto\">America\/Regina<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"16\"><span data-contrast=\"auto\">Canada Central Standard Time<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td data-celllook=\"4352\"><span data-contrast=\"auto\">Manitoba<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"256\"><span data-contrast=\"auto\">America\/Cancun<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"272\"><span data-contrast=\"auto\">Eastern Standard Time (Mexico)<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span data-contrast=\"auto\">Configure the matching IANA zone in the SQL Server service or container\u2019s <\/span><span data-contrast=\"auto\">TZ<\/span><span data-contrast=\"auto\"> environment, or through the applicable host configuration. Ensure the setting reaches the <\/span><b><span data-contrast=\"auto\">SQL Server process<\/span><\/b><span data-contrast=\"auto\">, not only an interactive shell; restart or redeploy that process as appropriate. <\/span><span data-contrast=\"auto\">TZ<\/span><span data-contrast=\"auto\"> takes precedence over <\/span><span data-contrast=\"auto\">\/etc\/localtime<\/span><span data-contrast=\"auto\"> and the other documented configuration sources.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Do not assume that updating Linux <\/span><span data-contrast=\"auto\">tzdata<\/span><span data-contrast=\"auto\"> alone updates SQL Server\u2019s Windows-zone definitions or mapping. For older releases, use the corresponding <\/span><a href=\"https:\/\/learn.microsoft.com\/en-us\/sql\/linux\/configure\/time-zone-2019?view=sql-server-ver17\"><span data-contrast=\"none\">SQL Server 2019<\/span><\/a><span data-contrast=\"auto\"> or <\/span><a href=\"https:\/\/learn.microsoft.com\/en-us\/sql\/linux\/configure\/time-zone-2017?view=sql-server-ver17\"><span data-contrast=\"none\">SQL Server 2017<\/span><\/a><span data-contrast=\"auto\"> documentation.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<h2><b><span data-contrast=\"none\">Azure SQL Database<\/span><\/b><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\n<p><span data-contrast=\"auto\">As described in <\/span><a href=\"https:\/\/devblogs.microsoft.com\/azure-sql\/announcing-the-public-preview-of-local-time-zone-support-in-azure-sql-database\/\"><span data-contrast=\"none\">my earlier announcement of local time zone support<\/span><\/a><span data-contrast=\"auto\">, the public-preview feature allows configuration at the <\/span><b><span data-contrast=\"auto\">database or session level<\/span><\/b><span data-contrast=\"auto\">.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">For example, use the following options for Manitoba:<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<pre class=\"prettyprint language-sql\"><code class=\"language-sql\">-- Persistent database default\r\nALTER DATABASE SCOPED CONFIGURATION\r\nSET TIME_ZONE = 'Eastern Standard Time (Mexico)';\r\n\r\n-- Alternatively, override just the current connection\r\nSET TIME ZONE 'Eastern Standard Time (Mexico)';\u00a0\u00a0<\/code><\/pre>\n<p><span data-contrast=\"auto\">A session override takes precedence over the database setting. <\/span><span data-contrast=\"auto\">SET TIME ZONE LOCAL<\/span><span data-contrast=\"auto\"> removes the session override.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Inside a stored procedure or dynamic SQL batch, the change is scoped to that execution. A normal <\/span><span data-contrast=\"auto\">GO<\/span><span data-contrast=\"auto\"> batch separator does <\/span><b><span data-contrast=\"auto\">not<\/span><\/b><span data-contrast=\"auto\"> reset a session setting. See the <\/span><a href=\"https:\/\/learn.microsoft.com\/en-us\/sql\/t-sql\/statements\/set-time-zone-transact-sql?view=azuresqldb-current\"><span data-contrast=\"none\">SET TIME ZONE documentation<\/span><\/a><span data-contrast=\"auto\"> for scope and usage details.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">The setting affects current-time functions such as <\/span><span data-contrast=\"auto\">GETDATE()<\/span><span data-contrast=\"auto\">, <\/span><span data-contrast=\"auto\">SYSDATETIME()<\/span><span data-contrast=\"auto\">, and <\/span><span data-contrast=\"auto\">SYSDATETIMEOFFSET()<\/span><span data-contrast=\"auto\">. It does <\/span><b><span data-contrast=\"auto\">not<\/span><\/b><span data-contrast=\"auto\"> convert stored values, change explicit <\/span><span data-contrast=\"auto\">AT TIME ZONE<\/span><span data-contrast=\"auto\"> expressions, or change UTC timestamps in system views.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Once the regional identifier becomes available, replace the interim setting at the scope your application uses. <\/span><span data-contrast=\"auto\">SET TIME ZONE<\/span><span data-contrast=\"auto\"> is not supported on SQL Server.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<h2><b><span data-contrast=\"none\">Azure SQL Managed Instance<\/span><\/b><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\n<p><span data-contrast=\"auto\">The <\/span><strong><a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/azure-sql\/managed-instance\/timezones-overview?view=azuresql\">instance time zone can only be selected during creation<\/a><\/strong><span data-contrast=\"auto\">. To change the instance-level time zone itself, create a replacement instance with the required temporary or final time zone and migrate the workload.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">On SQL Managed Instances using the <\/span><a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/azure-sql\/managed-instance\/update-policy?view=azuresql\"><span data-contrast=\"none\">Always-up-to-date update policy<\/span><\/a><span data-contrast=\"auto\"> where local time zone support is available, use <\/span><span data-contrast=\"auto\">ALTER DATABASE SCOPED CONFIGURATION SET TIME_ZONE<\/span><span data-contrast=\"auto\"> or <\/span><span data-contrast=\"auto\">SET TIME ZONE<\/span><span data-contrast=\"auto\"> to apply the same interim time zones at database or session scope. These settings change the effective time zone for supported current-time functions without migrating the instance. They do not change the instance-level time zone or SQL Agent schedules; an instance-wide time zone change still requires the migration approach below.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:0,&quot;335551620&quot;:0,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<table data-tablestyle=\"MsoTableGrid\" data-tablelook=\"1696\">\n<tbody>\n<tr>\n<td data-celllook=\"69633\"><b><span data-contrast=\"auto\">Migration option<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td data-celllook=\"65537\"><b><span data-contrast=\"auto\">How it works<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<td data-celllook=\"65553\"><b><span data-contrast=\"auto\">Trade-off and requirements<\/span><\/b><span data-ccp-props=\"{&quot;335551550&quot;:2,&quot;335551620&quot;:2}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td data-celllook=\"4096\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/azure-sql\/managed-instance\/failover-group-sql-mi?view=azuresql#overview\"><span data-contrast=\"none\">Failover group<\/span><\/a><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Replicate continuously, then perform a controlled planned failover after synchronization.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"16\"><span data-contrast=\"auto\">More setup; generally lower cutover downtime. Instances must be in different regions and share a DNS zone.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td data-celllook=\"4352\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/azure\/azure-sql\/managed-instance\/point-in-time-restore?view=azuresql&amp;tabs=azure-portal#restore-to-the-same-subscription\"><span data-contrast=\"none\">Cross-instance point-in-time restore<\/span><\/a><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"256\"><span data-contrast=\"auto\">Restore databases to a replacement instance in the same region, then cut applications over.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td data-celllook=\"272\"><span data-contrast=\"auto\">Simpler; generally longer downtime. Coordinate source writes and the final restore point to avoid omitting later transactions. Restore-point timestamps are interpreted as UTC.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span data-contrast=\"auto\">Recreate instance-level dependencies, including logins, objects in <\/span><span data-contrast=\"auto\">master<\/span><span data-contrast=\"auto\">, SQL Agent jobs, credentials, linked servers, certificates, SSIS packages and server-level configuration. Validate applications and job schedules before retiring the old instance.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<h3><b><span data-contrast=\"none\">Plan for two migrations when using an interim time zone<\/span><\/b><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:281,&quot;335559739&quot;:281}\">\u00a0<\/span><\/h3>\n<p><span data-contrast=\"auto\">If the final regional zone is unavailable, first migrate to an instance configured with the interim zone. After the regional zone becomes available, migrate again to another instance created with that final zone.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">For a failover-group approach that returns to the original region:<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><b><span data-contrast=\"auto\">Original MI \u2014 Region 1 \u2192 Temporary-zone MI \u2014 Region 2 \u2192 Final-zone MI \u2014 Region 1<\/span><\/b><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">The service update <\/span><b><span data-contrast=\"auto\">does not change the selected time zone of the existing temporary instance<\/span><\/b><span data-contrast=\"auto\">. Budget for both migrations and their cutovers.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Normally, failover-group partners should use matching time zones. A deliberate mismatch for this migration requires careful validation; it is not the recommended steady-state high-availability configuration.<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">If only a query or display requires adjustment, an explicit conversion can avoid changing instance-local time:<\/span><span data-ccp-props=\"{&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\n<pre class=\"prettyprint language-sql\"><code class=\"language-sql\">SELECT SYSUTCDATETIME() AT TIME ZONE 'UTC'\r\n\u00a0\u00a0\u00a0 AT TIME ZONE 'Eastern Standard Time (Mexico)' AS ManitobaLocalTime;\u00a0\u00a0<\/code><\/pre>\n<p><span data-contrast=\"auto\">This changes the query result\u2014not SQL Agent schedules or the instance\u2019s <\/span><span data-contrast=\"auto\">GETDATE()<\/span><span data-contrast=\"auto\"> behavior.<\/span><\/p>\n<h2>Azure SQL Managed Instance guide for impact analysis, discovery and planning<\/h2>\n<p>In this section, we will cover steps to help with the impact analysis, discovery of your resources and planning of the migration. This is NOT a prescriptive or complete guidance since the same analysis need to be applied to the OS environments (Windows, Linux), runtime (Python, Java), libraries and other downstream dependencies. Follow the guidance provided by the OS vendor, runtime owner, and library owner on how to obtain the latest time zone updates and update your environment or application.<\/p>\n<h2>Step 1: Discover affected Azure SQL Managed Instances<\/h2>\n<p>In order to identify the Azure SQL Managed instances in your organization that is configured with one of the affected time zones, you can execute the below PowerShell script from <a href=\"https:\/\/learn.microsoft.com\/azure\/cloud-shell\/overview\">Azure Cloud Shell<\/a> (PowerShell), or Windows PowerShell 5.1 \/ 7 with the <a href=\"https:\/\/learn.microsoft.com\/cli\/azure\/install-azure-cli\">Azure CLI<\/a> installed (run az login first). You need Reader access on the subscriptions you want to check.<\/p>\n<p><a href=\"https:\/\/raw.githubusercontent.com\/microsoft\/sql-server-samples\/refs\/heads\/master\/samples\/features\/time-zone\/inventory-sqlmi-servers.ps1\">Inventory SQLMI Instances (Powershell)<\/a><\/p>\n<p>The script will provide an output like below with the list of servers, a summary table and potential action(s) to perform.<\/p>\n<table style=\"border-collapse: collapse;width: 100%;height: 144px\">\n<tbody>\n<tr style=\"height: 24px\">\n<td style=\"width: 19.5597%;height: 24px\" width=\"110\"><strong>Impact<\/strong><\/td>\n<td style=\"width: 21.0838%;height: 24px\" width=\"119\"><strong>Instance<\/strong><\/td>\n<td style=\"width: 12.2777%;height: 24px\" width=\"68\"><strong>State<\/strong><\/td>\n<td style=\"width: 12.2777%;height: 24px\" width=\"68\"><strong>Fix<\/strong><\/td>\n<td style=\"width: 21.8459%;height: 24px\" width=\"68\"><strong>Policy<\/strong><\/td>\n<td style=\"width: 12.9551%;height: 24px\" width=\"63\"><strong>TimeZone<\/strong><\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 19.5597%;height: 24px\"><strong>&#8212;&#8212;<\/strong><\/td>\n<td style=\"width: 21.0838%;height: 24px\"><strong>&#8212;&#8212;&#8211;<\/strong><\/td>\n<td style=\"width: 12.2777%;height: 24px\"><strong>&#8212;&#8211;<\/strong><\/td>\n<td style=\"width: 12.2777%;height: 24px\"><strong>&#8212;<\/strong><\/td>\n<td style=\"width: 21.8459%;height: 24px\"><strong>&#8212;&#8212;<\/strong><\/td>\n<td style=\"width: 12.9551%;height: 24px\"><strong>&#8212;&#8212;&#8211;<\/strong><\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 19.5597%;height: 24px\">Yes (Alberta)<\/td>\n<td style=\"width: 21.0838%;height: 24px\">sqlmi-finance-prod<\/td>\n<td style=\"width: 12.2777%;height: 24px\">Ready<\/td>\n<td style=\"width: 12.2777%;height: 24px\">D<\/td>\n<td style=\"width: 21.8459%;height: 24px\">AlwaysUpToDate<\/td>\n<td style=\"width: 12.9551%;height: 24px\">Mountain<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 19.5597%;height: 24px\">Yes (Alberta)<\/td>\n<td style=\"width: 21.0838%;height: 24px\">sqlmi-hr-dev<\/td>\n<td style=\"width: 12.2777%;height: 24px\">Ready<\/td>\n<td style=\"width: 12.2777%;height: 24px\">A+D or R<\/td>\n<td style=\"width: 21.8459%;height: 24px\">SQLServer2022<\/td>\n<td style=\"width: 12.9551%;height: 24px\">Mountain<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 19.5597%;height: 24px\">Check (Manitoba)<\/td>\n<td style=\"width: 21.0838%;height: 24px\">sqlmi-ops-prod<\/td>\n<td style=\"width: 12.2777%;height: 24px\">Ready<\/td>\n<td style=\"width: 12.2777%;height: 24px\">A+D or R<\/td>\n<td style=\"width: 21.8459%;height: 24px\">SQLServer2022<\/td>\n<td style=\"width: 12.9551%;height: 24px\">Central<\/td>\n<\/tr>\n<tr style=\"height: 24px\">\n<td style=\"width: 19.5597%;height: 24px\">No<\/td>\n<td style=\"width: 21.0838%;height: 24px\">sqlmi-sales-prod<\/td>\n<td style=\"width: 12.2777%;height: 24px\">Stopped<\/td>\n<td style=\"width: 12.2777%;height: 24px\">&#8211;<\/td>\n<td style=\"width: 21.8459%;height: 24px\">SQLServer2022<\/td>\n<td style=\"width: 12.9551%;height: 24px\">UTC<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<table style=\"border-collapse: collapse;width: 100%\">\n<tbody>\n<tr>\n<td style=\"width: 25.2329%\" width=\"110\"><strong>Impact<\/strong><\/td>\n<td style=\"width: 27.265%\" width=\"119\"><strong>Instances<\/strong><\/td>\n<td style=\"width: 15.834%\" width=\"68\"><strong>Running<\/strong><\/td>\n<td style=\"width: 15.834%\" width=\"68\"><strong>Fix D<\/strong><\/td>\n<td style=\"width: 15.834%\" width=\"68\"><strong>Fix A+D or R<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 25.2329%\"><strong>&#8212;&#8212;<\/strong><\/td>\n<td style=\"width: 27.265%\"><strong>&#8212;&#8212;&#8212;<\/strong><\/td>\n<td style=\"width: 15.834%\"><strong>&#8212;&#8212;-<\/strong><\/td>\n<td style=\"width: 15.834%\"><strong>&#8212;&#8211;<\/strong><\/td>\n<td style=\"width: 15.834%\"><strong>&#8212;&#8212;&#8212;&#8212;<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 25.2329%\">Yes (Alberta)<\/td>\n<td style=\"width: 27.265%\">2<\/td>\n<td style=\"width: 15.834%\">2<\/td>\n<td style=\"width: 15.834%\">1<\/td>\n<td style=\"width: 15.834%\">1<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 25.2329%\">Check (Manitoba)<\/td>\n<td style=\"width: 27.265%\">1<\/td>\n<td style=\"width: 15.834%\">1<\/td>\n<td style=\"width: 15.834%\">0<\/td>\n<td style=\"width: 15.834%\">1<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 25.2329%\">No<\/td>\n<td style=\"width: 27.265%\">1<\/td>\n<td style=\"width: 15.834%\">0<\/td>\n<td style=\"width: 15.834%\">0<\/td>\n<td style=\"width: 15.834%\">0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The table output can be read as follows:<\/p>\n<table>\n<tbody>\n<tr>\n<td width=\"96\"><strong>Column<\/strong><\/td>\n<td width=\"538\"><strong>Meaning<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><strong>Impact<\/strong><\/td>\n<td width=\"538\">Yes = Mountain time (Alberta).<\/p>\n<p>Check = Pacific or Central time: impacted only if the workload follows BC or Manitoba time (US Pacific \/ Central workloads are not affected).<\/p>\n<p>No = any other time zone, e.g. Eastern or UTC.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><strong>State<\/strong><\/td>\n<td width=\"538\">Ready = running. Stopped instances must be started before applying a fix.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><strong>Fix<\/strong><\/td>\n<td width=\"538\">D = set a database-level time zone.<\/p>\n<p>A+D = switch update policy then D<\/p>\n<p>R = Recreate the instance.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><strong>Policy<\/strong><\/td>\n<td width=\"538\">The instance update policy. The database-level time zone is only available on Always-up-to-date.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><strong>Summary<\/strong><\/td>\n<td width=\"538\">Counts per impact level: how many instances, how many running, and how many need each fix.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>NOTE:<\/strong> Even if the instance does not use one of the affected time zones, you need to check for any explicit time zone usage using AT TIME ZONE clause in the SQL code. This can be done by using the SQL script described in the next section. The same checks need to be performed on the downstream dependencies or applications.<\/p>\n<h2>Step 2:\u00a0Discover affected objects in the database<\/h2>\n<p>In order to facilitate discovery and analysis of the affected database objects for the SQLMI instances identified in step #1, you can execute the below SQL script in a database to get list of objects that use various date or time functions. The script is meant as an aid to identify the schema objects that are potentially affected and is not intended to be comprehensive. For example, this SQL script will not detect usage of date\/time functions in the SQL statements in applications or discover all references.<\/p>\n<p>If you are using Azure SQL Database, Azure SQL Managed Instance (Always-up-to-date &amp; SQL Server 2025 policy), SQL Server 2025 or above, then use below script:<\/p>\n<p><a href=\"https:\/\/raw.githubusercontent.com\/microsoft\/sql-server-samples\/refs\/heads\/master\/samples\/features\/time-zone\/date-time-usage-discovery.sql\">Date time usage discovery script (SQL Server 2025 version)<\/a><\/p>\n<p>If you are using Azure SQL Managed Instance (SQL Server 2022 policy), SQL Server 2022 or earlier, then use below script:<\/p>\n<p><a href=\"https:\/\/raw.githubusercontent.com\/microsoft\/sql-server-samples\/refs\/heads\/master\/samples\/features\/time-zone\/date-time-usage-discovery-sql2022.sql\">Date time usage discovery script (SQL Server 2022 or lower version)<\/a><\/p>\n<h2>Step 3: Decide on the approach for each affected instance<\/h2>\n<p>For each impacted instance, follow the decision tree. For the path with no impact also, access use of AT TIME ZONE clause or other conversions in the SQL code. Use of AT TIME ZONE clause in your SQL objects will be highlighted in by the discovery script in step #2.<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2026\/10\/Time-zone-migration-tree.webp\"><img decoding=\"async\" class=\"alignnone wp-image-7853 size-full\" src=\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2026\/10\/Time-zone-migration-tree.webp\" alt=\"Time zone migration 8211 tree image\" width=\"586\" height=\"720\" srcset=\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2026\/10\/Time-zone-migration-tree.webp 586w, https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2026\/10\/Time-zone-migration-tree-244x300.webp 244w\" sizes=\"(max-width: 586px) 100vw, 586px\" \/><\/a><\/p>\n<h2>Step 4: Take action<\/h2>\n<p>Perform the migration of databases to the SQL Managed instance following your existing deployment methodology. Validate the process in a test environment with all the dependencies before migrating the production environment.<\/p>\n<h2>Frequently asked questions<\/h2>\n<table style=\"width: 91.8042%\">\n<tbody>\n<tr>\n<td style=\"width: 59.3272%\" width=\"250\"><strong>Question<\/strong><\/td>\n<td style=\"width: 115.292%\" width=\"384\"><strong>Answer<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 59.3272%\" width=\"250\"><strong>Can I change the time zone of my existing Azure SQL Managed instance?<\/strong><\/td>\n<td style=\"width: 115.292%\" width=\"384\">No. Use the database-level time zone or recreate the instance.<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 59.3272%\" width=\"250\"><strong>Will the database-level time zone come to Azure SQL Managed instances with the SQL Server 2022\/2025 update policy?<\/strong><\/td>\n<td style=\"width: 115.292%\" width=\"384\">No. It is available only with the Always-up-to-date update policy.<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 59.3272%\" width=\"250\"><strong>Does the database-level time zone change in Azure SQL Managed with always-up-to-date policy affect time conversions in SQL Agent, SSIS packages or OS scripts?<\/strong><\/td>\n<td style=\"width: 115.292%\" width=\"384\">No. Agent schedules follow the instance time zone &#8211; update them separately. SSIS packages, OS scripts or other external artifacts follow the instance time zone.<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 59.3272%\" width=\"250\"><strong>Do I have to wait for the Windows update?<\/strong><\/td>\n<td style=\"width: 115.292%\" width=\"384\">No. Use the interim zones today and switch to the final time zone later.<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 59.3272%\" width=\"250\"><strong>Should I change historical conversions to the interim zone?<\/strong><\/td>\n<td style=\"width: 115.292%\" width=\"384\">No. Interim time zone match current and future offsets only, not historical rules.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Learn more<\/h2>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/azure\/azure-sql\/managed-instance\/timezones-overview\">Time zones in Azure SQL Managed Instance<\/a><\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/azure\/azure-sql\/managed-instance\/update-policy\">Update policy in Azure SQL Managed Instance<\/a><\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/azure\/azure-sql\/managed-instance\/point-in-time-restore\">Point-in-time restore<\/a> |\u00a0 <a href=\"https:\/\/learn.microsoft.com\/azure\/azure-sql\/managed-instance\/failover-group-sql-mi\">Failover groups<\/a><\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/sql\/t-sql\/statements\/alter-database-scoped-configuration-transact-sql\">ALTER DATABASE SCOPED CONFIGURATION<\/a> |\u00a0 <a href=\"https:\/\/learn.microsoft.com\/sql\/t-sql\/statements\/set-time-zone-transact-sql\">SET TIME ZONE<\/a>\u00a0 |\u00a0 <a href=\"https:\/\/learn.microsoft.com\/sql\/relational-databases\/system-catalog-views\/sys-time-zone-info-transact-sql\">time_zone_info<\/a><\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/azure\/azure-sql\/managed-instance\/job-automation-managed-instance\">SQL Agent in SQL Managed Instance | <\/a><a href=\"https:\/\/learn.microsoft.com\/sql\/relational-databases\/system-stored-procedures\/sp-update-schedule-transact-sql\">sp_update_schedule<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Affected locations in British Columbia, Alberta, and Manitoba will not turn their clocks back at 02:00 local time on November 1, 2026. They will remain at UTC\u221207:00, UTC\u221206:00, and UTC\u221205:00, respectively.\u00a0 Microsoft\u2019s interim guidance for British Columbia, Alberta, and Manitoba describes the new Windows time zones and temporary workarounds.\u00a0 SQL Server on Windows requires the [&hellip;]<\/p>\n","protected":false},"author":92817,"featured_media":81,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,656,572,619],"tags":[510,636,726,552,34],"class_list":["post-7808","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-sql","category-fabric-sql-database","category-managed-instance","category-t-sql","tag-azure-sql-database","tag-azure-sql-managed-instance","tag-fabric-sql","tag-sql-server","tag-t-sql"],"acf":[],"blog_post_summary":"<p>Affected locations in British Columbia, Alberta, and Manitoba will not turn their clocks back at 02:00 local time on November 1, 2026. They will remain at UTC\u221207:00, UTC\u221206:00, and UTC\u221205:00, respectively.\u00a0 Microsoft\u2019s interim guidance for British Columbia, Alberta, and Manitoba describes the new Windows time zones and temporary workarounds.\u00a0 SQL Server on Windows requires the [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts\/7808","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/users\/92817"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/comments?post=7808"}],"version-history":[{"count":2,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts\/7808\/revisions"}],"predecessor-version":[{"id":7915,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/posts\/7808\/revisions\/7915"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/media\/81"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/media?parent=7808"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/categories?post=7808"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-json\/wp\/v2\/tags?post=7808"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}