Open jonsamwell opened 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
Author: | jonsamwell |
---|---|
Assignees: | - |
Labels: | `SQL`, `Service Attention` |
Milestone: | - |
sql
I've seen this same behaviour from Azure DevOps CLI Step. (windows-2019 hosted agent) and it was working fine and then in the last couple of weeks it has stopped working with the same error.
Still noticing the same as @binarysenator from Azure DevOps CLI - worked fine up to a few weeks back, I think it changed beginning this year - no specific error message, the "import db" job keeps running and eventually times out after 30min
Does this happen with the powershell command New-AzSqlDatabaseImport as well, or is it specific to CLI? If it happens with powershell as well, does the operation appear in the azure portal? If so, what is the status there?
Describe the bug Using the
az sql db import
with a bacpac (with a size of 2.5mb) located in azure storage fails eventually after roughtly 30 minutes even if I import into a DB on a very powerful tier i.e. P6 or above. I've tried increasing the size of the blank database (P6) it is imported into but nothing works.To Reproduce
Expected behavior The import operation runs to completion
Environment summary Running on AzureDevops hosted agent windows-latest
Additional context Debug logs
It goes on trying the
importExportOperationResults
call for about 20 minutes then fails with the below: