Skip to content

Commit 80d3e2d

Browse files
authored
Merge pull request #85058 from MladjoA/master
Removing time zone + PITR issue related content as fixed
2 parents 7d957a3 + 6f53fa2 commit 80d3e2d

File tree

2 files changed

+1
-9
lines changed

2 files changed

+1
-9
lines changed

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

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

7878
### Point-in-time restore
7979

80-
<del>When you perform a point-in-time restore, the time to restore to is interpreted as UTC time. This setting avoids any ambiguity due to daylight saving time and its potential changes.<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. See [Known issues](sql-database-managed-instance-timezone.md#known-issues) for more details.
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.
8481

8582
### Auto-failover groups
8683

articles/sql-database/sql-database-managed-instance-transact-sql-information.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -621,11 +621,6 @@ You can't execute `BACKUP DATABASE ... WITH COPY_ONLY` on a database that's encr
621621

622622
**Workaround:** Use automatic backups and point-in-time restore, or use [customer-managed (BYOK) TDE](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-azure-sql#customer-managed-transparent-data-encryption---bring-your-own-key) instead. You also can disable encryption on the database.
623623

624-
### Point-in-time restore follows time by the time zone set on the source instance
625-
626-
Point-in-time restore currently interprets time to restore to by following time zone of the source instance instead by following UTC.
627-
Check [managed instance time zone known issues](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-timezone#known-issues) for more details.
628-
629624
## Next steps
630625

631626
- For more information about managed instances, see [What is a managed instance?](sql-database-managed-instance.md)

0 commit comments

Comments
 (0)