[SQL] az sql db update: Add --manual-cutover and --perform-cutover arguments
#28938
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eporting from CLI
…nto FMv2_202404
️✔️AzureCLI-FullTest
|
|
Hi @mohitagarwal-sql, |
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| sql db update | cmd sql db update added parameter manual_cutover |
||
| sql db update | cmd sql db update added parameter perform_cutover |
|
SQL |
microsoft-github-policy-service
bot
added
Auto-Assign
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
mohitagarwal-sql
changed the title
az sql db update: Add --manual-cutover and --perform-cutover arguments
evelyn-ys
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related command
az sql db update -g $resourceGroupName -s $serverName -n $databaseName --edition Hyperscale --service-objective $serviceObjective --no-wait --manual-cutoveraz sql db update -g $resourceGroupName -s $serverName -n $databaseName --no-wait --perform-cutoverDescription
When doing Update-SLO from GeneralPurpose/BusinessCritical/Basic/Standard/Premium to Hyperscale, the cutover to make Hyperscale as Primary database is automatic and cannot be controlled by Customer. To provide flexibility to the Customer, a parameter named 'manual-cutover' is provided to Customer which can be provided while initiating database update to Hyperscale tier. The update operation will wait for Customer/user to trigger cutover as and when needed using another argument called as 'perform-cutover' to make Hyperscale database as new user database.
Testing Guide
az sql db create -g $resourceGroupName -s $serverName -n $databaseName --edition GeneralPurpose --service-objective GP_Gen5_2az sql db update -g $resourceGroupName -s $serverName -n $databaseName --edition Hyperscale --service-objective HS_Gen5_2 --no-wait --manual-cutoveraz sql db update -g $resourceGroupName -s $serverName -n $databaseName --no-wait --perform-cutoverHistory Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.