SQL resource provider 22.214.171.124 release notes
Applies to: Azure Stack integrated systems and Azure Stack Development Kit
These release notes describe the improvements and known issues in SQL resource provider version 126.96.36.199.
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 build. The minimum Azure Stack release version required to install this version of the SQL resource provider is listed below:
Minimum Azure Stack version SQL resource provider version Version 1808 (1.1808.0.97) 188.8.131.52
Apply the minimum supported Azure Stack update to your Azure Stack integrated system or deploy the latest Azure Stack Development Kit (ASDK) before deploying the latest version of the SQL resource provider.
New features and fixes
This version of the Azure Stack SQL resource provider includes the following improvements and fixes:
Telemetry enabled for SQL resource provider deployments. Telemetry collection has been enabled for SQL resource provider deployments. Telemetry collected includes resource provider deployment, start and stop times, exit status, exit messages, and error details (if applicable).
TLS 1.2 encryption update. Enabled TLS 1.2-only support for resource provider communication with internal Azure Stack components.
SQL resource provider Azure Stack PowerShell compatibility. The SQL resource provider has been updated to work with the Azure Stack 2018-03-01-hybrid PowerShell profile and to provide compatibility with AzureRM 1.3.0 and later.
SQL login change password blade. Fixed an issue where the password can't be changed on the change password blade. Removed links from password change notifications.
SQL hosting server settings blade update. Fixed an issue where the settings blade was incorrectly titled as "Password".
SQL SKUs can take up to an hour to be visible in the portal. It can take up to an hour for newly created SKUs to be visible for use when creating new SQL databases.
Reused SQL logins. Attempting to create a new SQL login with the same username as an existing login under the same subscription will result in reusing the same login and the existing password.
Workaround: Use different usernames when creating new logins under the same subscription or create logins with the same username under different subscriptions.
Shared SQL logins cause data inconsistency. If a SQL login is shared for multiple SQL databases under the same subscription, changing the login password will cause data inconsistency.
Workaround: Always use different logins for different databases under the same subscription.
TLS 1.2 support requirement. If you try to deploy or update the SQL resource provider from a computer where TLS 1.2 is not enabled, the operation might fail. Run the following PowerShell command on the computer being used to deploy or update the resource provider to verify that TLS 1.2 is returned as supported:
If Tls12 is not included in the output of the command, TLS 1.2 is not enabled on the computer.
Workaround: Run the following PowerShell command to enable TLS 1.2 and then start the resource provider deployment or update script from the same PowerShell session:
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
SQL resource provider fails to add SQL Server Always On listener. When using the listener IP address of the SQL Server Always On Listener, the SQL resource provider VM cannot resolve the listener's host name.
Workaround: Ensure that DNS works correctly to resolve the listener IP to listener host name.
Known issues for Cloud Admins operating Azure Stack
Refer to the documentation in the Azure Stack Release Notes.