Skip to content

Commit a9fd360

Browse files
authored
Merge pull request #58055 from Antvgski/patch-2
Updated feature description
2 parents 4005476 + 2d1bb0f commit a9fd360

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sql-data-warehouse/maintenance-scheduling.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: 09/20/2018
10+
ms.date: 11/14/2018
1111
ms.author: anvang
1212
ms.reviewer: igorstan
1313
---
@@ -22,7 +22,7 @@ All newly created Azure SQL Data Warehouse instances will have a system-defined
2222

2323
Each maintenance window can be three to eight hours. Maintenance can occur at any time within the window. You should expect a brief loss of connectivity as the service deploys new code to your data warehouse.
2424

25-
During the feature preview, you identify primary and secondary windows within separate day ranges. All maintenance operations should finish within the scheduled maintenance windows. No maintenance will take place outside the specified maintenance windows without prior notification. If your data warehouse is paused during a scheduled maintenance, it will be updated during the resume operation.
25+
To use this feature you will need to identify a primary and secondary window within separate day ranges. All maintenance operations should finish within the scheduled maintenance windows. No maintenance will take place outside the specified maintenance windows without prior notification. If your data warehouse is paused during a scheduled maintenance, it will be updated during the resume operation.
2626

2727

2828
## Alerts and monitoring

0 commit comments

Comments
 (0)