Open jvandertil opened 1 year ago
Thank you for opening this issue, we will look into it.
Adding the service-level-objective
parameter does seem to work. If this is intended, then this is probably a documentation issue?
az sql db ltr-backup restore --backup-id "$($backupToRestore.id)" `
--dest-resource-group $DestinationResourceGroup `
--dest-server $DestinationServer `
--dest-database $DestinationDatabaseName `
--tier "Standard" `
--capacity 100 `
--service-level-objective "S3"
--debug
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
Author: | jvandertil |
---|---|
Assignees: | - |
Labels: | `bug`, `SQL`, `Service Attention`, `question`, `customer-reported`, `Auto-Assign` |
Milestone: | Backlog |
@grrlgeek is this something you may have some insight into?
This was the document I came across - https://learn.microsoft.com/en-us/cli/azure/sql/db/ltr-backup?view=azure-cli-latest.
As @jvandertil mentioned, adding the service-level-objective
parameter seems to have solved the issue which indicates that this is a required parameter. However in the documentation, this parameter is listed as optional. Perhaps, we need to update? Couldn't locate the author(s) of this article to tag them unfortunately
Describe the bug
When trying to restore a Azure SQL Database using the DTU model the command fails with what seems to be an invalid request to Azure.
Related command
az sql db ltr-backup restore
Errors
(InvalidRequestContent) The request content was invalid and could not be deserialized: Required property 'name' not found in 'sku'. Code: InvalidRequestContent Message: The request content was invalid and could not be deserialized: Required property 'name' not found in 'sku'.
Issue script & Debug output
Script:
Debug log:
Expected behavior
Database backup restore is started
Environment Summary
azure-cli 2.49.0
core 2.49.0 telemetry 1.0.8
Dependencies: msal 1.20.0 azure-mgmt-resource 22.0.0
Additional context
No response