Closed IrangaSubasingheMSFT closed 2 years ago
@IrangaSubasingheMSFT Thanks for your feedback! We will investigate and update as appropriate.
@cawrites In this documentation it says that Backpac export/Import from Azure Portal, Azure portal, from PowerShell using New-AzSqlDatabaseExport or New-AzSqlDatabaseImport, from Azure CLI using az sql db export and az sql db import, and from REST API is not supported.
In this Documentation it says you can submit a database request using Powershell however this does not work for Hyperscale.
@LitKnd Could you please take a look at this issue? Thank you! #reassign:LitKnd
Hi @IrangaSubasingheMSFT ,
Thanks for raising this issue. We have incorporated a change into the 'Export an Azure SQL Database to a BACPAC file' article to clarify the limitations for Hyperscale per your suggestion. The pull request for this has been signed off on and I expect this to publish today, or within the next couple of business days at the latest.
Thanks again for helping make our docs better! Kendra
Kendra Little SQL Docs Team
Hi @GeethaThatipatri-MSFT
Could you point me to the link which clearly mentions about the Database Export Limitation for Hyperscale ? I checked the links none have the update ?
This page should have this clearly mentioned: https://learn.microsoft.com/en-us/azure/azure-sql/database/database-export?view=azuresql-mi
In the Azure SQL DB page should mention the limitation saying that the PowerShell and Portal export operation is not supported clearly as this is a feature many customers would use for exporting the databases to storage accounts. Prefer it can be mentioned here: https://docs.microsoft.com/en-us/azure/azure-sql/database/database-export#powershell
The limitation currently mentioned in the https://docs.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale#known-limitations but its not prominent.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.