Skip to content

Commit 60606c5

Browse files
authored
Merge pull request #75458 from MicrosoftDocs/master
Hotfix
2 parents 807c318 + ce7e731 commit 60606c5

File tree

3 files changed

+171
-135
lines changed

3 files changed

+171
-135
lines changed

articles/sql-data-warehouse/gen2-migration-schedule.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The following table summarizes by region when the Lower Gen2 compute tier will b
6161

6262
## Automatic upgrade process
6363

64-
Based on the availability chart above, we'll be scheduling automated upgrades for your Gen1 instances. To avoid any unexpected interruptions on the availability of the data warehouse, the automated upgrades will be scheduled during your maintenance schedule. For more information on schedules, see [View a maintenance schedule](viewing-maintenance-schedule.md)
64+
Based on the availability chart above, we'll be scheduling automated upgrades for your Gen1 instances. To avoid any unexpected interruptions on the availability of the data warehouse, the automated upgrades will be scheduled during your maintenance schedule. The ability to create a new Gen1 instance will be disabled in regions undergoing auto upgrade to Gen2. For more information on schedules, see [View a maintenance schedule](viewing-maintenance-schedule.md)
6565

6666
The upgrade process will involve a brief drop in connectivity (approximately 5 min) as we restart your data warehouse. Once your data warehouse has been restarted, it will be fully available for use. However, you may experience a degradation in performance while the upgrade process continues to upgrade the data files in the background. The total time for the performance degradation will vary dependent on the size of your data files.
6767

0 commit comments

Comments
 (0)