Skip to content

Commit 02c555a

Browse files
committed
Putting PITR timezone issue back as train with the fix has been rolled out
1 parent 30fa3cc commit 02c555a

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/sql-database/sql-database-managed-instance-timezone.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,10 @@ You can restore a backup file or import data to a managed instance from an insta
7777

7878
### Point-in-time restore
7979

80-
When you perform a point-in-time restore, the time to restore to is interpreted as UTC time. This way any ambiguities due to daylight saving time and its potential changes are avoided.
80+
<del>When you perform a point-in-time restore, the time to restore to is interpreted as UTC time. This way any ambiguities due to daylight saving time and its potential changes are avoided.<del>
81+
82+
>[!WARNING]
83+
> Current behavior is not in line with the statement above, and time to restore to is interpreted as per the time zone of the source managed instance where automatic database backups are taken from. We are working on correcting this behavior to interpret given point in time as UTC time.
8184
8285
### Auto-failover groups
8386

0 commit comments

Comments
 (0)