Skip to content

Commit 785a2b5

Browse files
authored
Merge pull request #85389 from MladjoA/master
Putting PITR timezone issue back
2 parents f7d02d1 + 5c2e3cd commit 785a2b5

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: conceptual
99
author: MladjoA
1010
ms.author: mlandzic
1111
ms.reviewer:
12-
ms.date: 08/12/2019
12+
ms.date: 08/14/2019
1313
---
1414
# Time zones in Azure SQL Database Managed Instance
1515

@@ -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)