SQL resource provider 1.1.93.x release notes

These release notes describe the improvements and known issues in SQL resource provider version 1.1.93.x.

Build reference

Download the SQL resource provider binary and then run the self-extractor to extract the contents to a temporary directory. The resource provider has a minimum corresponding Azure Stack Hub build. The minimum Azure Stack Hub release version required to install this version of the SQL resource provider is listed below:

Supported Azure Stack Hub version SQL resource provider version
Version 2102, 2008, 2005 SQL RP version


Apply the minimum supported Azure Stack Hub update to your Azure Stack Hub integrated system before deploying the latest version of the MySQL resource provider.

New features and fixes

This version of the Azure Stack Hub SQL resource provider includes the following improvements and fixes:

  • Update the base VM to a specialized Windows Server. This Windows Server version is specialize for Azure Stack Hub Add-On RP Infrastructure and it is not visible to the tenant marketplace. Make sure to download the Microsoft AzureStack Add-On RP Windows Server image before deploying or upgrading to this version of the SQL resource provider.
  • Support removing orphaned database metadata and hosting server metadata. When a hosting server cannot be connected anymore, the tenant will have an option to remove the orphaned database metadata from the portal. When there is no orphaned database metadata linked to the hosting server, the operator will be able to remove the orphaned hosting server metadata from the admin portal.
  • Make KeyVaultPfxPassword an optional argument when performing secrets rotation. Check this document for details.
  • Other bug fixes.

It's recommended that you apply SQL resource provider after Azure Stack Hub is upgraded to the 2005 release.

Known issue

Deployment of version may fail if the wrong AzureRmContext is used. It is recommended to upgrade to version directly.

When redeploying the SQL resource provider while the same version had deployed already (for example, when SQL resource provider is already deployed, and the same version is deployed again), the VM that is hosting the SQL resource provider will be stopped. To fix this issue, go to the admin portal, locate and restart the VM named sqlvm<version> in the resource group named system.<region>.sqladapter.

Next steps