Update conversion instructions for Hyperscale pools#10339
Conversation
Added information about conversion from zone redundant elastic pools to Hyperscale pools.
prmerger-automator
Bot
requested review from
WilliamDAssafMSFT and
dimitri-furman
|
@allanhirt : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 8abd590: ✅ Validation status: passed
For more details, please refer to the build report. |
|
|
||
| - Direct conversion from the Basic service tier to Hyperscale isn't supported. To perform this conversion, first change the database to any service tier other than Basic (for example, General Purpose), and then proceed with the conversion to Hyperscale. | ||
|
|
||
| - Direct coversion from a zone redundant elastic pool to a non-zone redundant Hyperscale pool is not supported. To perform this conversion, first convert the pool to standalone bu choosing an offering such as Business Critical. Then remove zone redundancy and changet the service tier to Hyperscale. At that point, the database can be added to an existing, non-zone redundant Hyperscale pool or one could be created and the database added. |
There was a problem hiding this comment.
I can't find a way to edit again, but it should be "conversion", not "coversion"
There was a problem hiding this comment.
Also, it should be "by", not "bu" and "changet" to "change".
There was a problem hiding this comment.
Hi @allanhirt, thanks for creating this PR. We'll review.
Right away - Go to Files Changed, the ... menu, then Edit to make more edits. You can add more than one commit to this branch. Shortcut: https://github.com/allanhirt/sql-docs/edit/patch-43/azure-sql/database/convert-to-hyperscale.md?pr=/MicrosoftDocs/sql-docs/pull/10339
I've marked this PR as a draft. You can click on Ready for review when you're ready for us to review.
There was a problem hiding this comment.
Where do I select "Ready for review"?
There was a problem hiding this comment.
Button near the bottom, in the Review Requested block.
Corrected typos and improved clarity in the conversion instructions.
WilliamDAssafMSFT
requested review from
Copilot
and removed request for
WilliamDAssafMSFT
|
Learn Build status updates of commit 699c41c: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Updates Hyperscale conversion documentation to cover an additional unsupported conversion path and cleans up related content formatting.
Changes:
- Add guidance for converting from a zone-redundant elastic pool to a non-zone-redundant Hyperscale pool (via intermediate steps).
- Fix a formatting/indentation issue in the “Related content” list.
|
|
||
| - Direct conversion from the Basic service tier to Hyperscale isn't supported. To perform this conversion, first change the database to any service tier other than Basic (for example, General Purpose), and then proceed with the conversion to Hyperscale. | ||
|
|
||
| - Direct conversion from a zone redundant elastic pool to a non-zone redundant Hyperscale pool is not supported. To perform this conversion, first convert the pool to standalone by choosing an offering such as Business Critical. Then remove zone redundancy and change the service tier to Hyperscale. At that point, the database can be added to an existing, non-zone redundant Hyperscale pool or one could be created and the database added. |
|
|
||
| - Direct conversion from the Basic service tier to Hyperscale isn't supported. To perform this conversion, first change the database to any service tier other than Basic (for example, General Purpose), and then proceed with the conversion to Hyperscale. | ||
|
|
||
| - Direct conversion from a zone redundant elastic pool to a non-zone redundant Hyperscale pool is not supported. To perform this conversion, first convert the pool to standalone by choosing an offering such as Business Critical. Then remove zone redundancy and change the service tier to Hyperscale. At that point, the database can be added to an existing, non-zone redundant Hyperscale pool or one could be created and the database added. |
There was a problem hiding this comment.
To perform this conversion, first convert the pool to standalone
@allanhirt Do you mean, first convert the database to standalone?
Clarified the process for converting a database from a zone-redundant elastic pool to a non-zone-redundant Hyperscale pool, specifying the need to remove the database from the pool and disable zone redundancy before conversion.
|
Learn Build status updates of commit 7c21f00: ✅ Validation status: passed
For more details, please refer to the build report. |
|
#label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Added information about conversion from zone redundant elastic pools to non-zone redundant Hyperscale pools.