Skip to content

Commit 4005476

Browse files
authored
Merge pull request #58059 from Antvgski/patch-3
Made an update to the steps
2 parents 299c095 + 03867bc commit 4005476

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sql-data-warehouse/changing-maintenance-schedule.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: craigg
77
ms.service: sql-data-warehouse
88
ms.topic: conceptual
99
ms.component: design
10-
ms.date: 10/07/2018
10+
ms.date: 10/15018
1111
ms.author: anvang
1212
ms.reviewer: igorstan
1313
---
@@ -17,7 +17,7 @@ ms.reviewer: igorstan
1717
## Portal
1818
A maintenance schedule can be updated or changed at any time. If the selected instance is going through an active maintenance cycle, the settings will be saved. They'll become active during the next identified maintenance period. [Learn more](https://docs.microsoft.com/azure/service-health/resource-health-overview) about monitoring your data warehouse during an active maintenance event.
1919

20-
While Azure maintenance schedules are in preview, you select two maintenance windows during a seven-day period. Each maintenance window can be three to eight hours. Maintenance can occur at any time within a maintenance window but won't occur outside time windows without prior notification. You'll also experience a brief loss of connectivity as the service deploys new code to your data warehouse.
20+
To use maintenance schedules, you must select two maintenance windows during a seven-day period. Each maintenance window can be three to eight hours. Maintenance can occur at any time within a maintenance window but won't occur outside time windows without prior notification. You'll also experience a brief loss of connectivity as the service deploys new code to your data warehouse.
2121

2222
## Identifying the primary and secondary windows
2323

0 commit comments

Comments
 (0)