Update the SQL resource provider
Before updating the resource provider, review the release notes to learn about new functionality, fixes, and any known issues that could affect your deployment. The release notes also specify the minimum Azure Stack Hub version required for the resource provider.
A new SQL resource provider might be released when Azure Stack Hub is updated to a new build. Although the existing resource provider continues to work, we recommend updating to the latest build as soon as possible.
|Supported Azure Stack Hub version||SQL RP version||Windows Server that RP service is running on|
|2102, 2008, 2005||SQL RP version 220.127.116.11||Microsoft AzureStack Add-on RP Windows Server|
|2005, 2002, 1910||SQL RP version 18.104.22.168||Windows Server 2016 Datacenter - Server Core|
|1908||SQL RP version 22.214.171.124||Windows Server 2016 Datacenter - Server Core|
SQL resource provider update is cumulative. When updating from an old version, you can directly update to the latest version.
To update the resource provider, use the UpdateSQLProvider.ps1 script. Use your service account with local administrative rights and is an owner of the subscription. This update script is included with the download of the resource provider.
The update process is similar to the process used to Deploy the resource provider. The update script uses the same arguments as the DeploySqlProvider.ps1 script, and you'll need to provide certificate information.
Update script processes
The UpdateSQLProvider.ps1 script creates a new virtual machine (VM) with the latest OS image, deploy the latest resource provider code, and migrates the settings from the old resource provider to the new resource provider.
We recommend that you download the latest Windows Server 2016 Core image or Microsoft AzureStack Add-on RP Windows Server image from Marketplace Management. If you need to install an update, you can place a single MSU package in the local dependency path. The script will fail if there's more than one MSU file in this location.
After the UpdateSQLProvider.ps1 script creates a new VM, the script migrates the following settings from the old resource provider VM:
- database information
- hosting server information
- required DNS record
We strongly recommend using Clear-AzureRmContext -Scope CurrentUser and Clear-AzureRmContext -Scope Process to clear the cache before running the deployment or update script.
Update script parameters
You can specify the following parameters from the command line when you run the UpdateSQLProvider.ps1 PowerShell script. If you don't, or if any parameter validation fails, you're prompted to provide the required parameters.
|Parameter name||Description||Comment or default value|
|CloudAdminCredential||The credential for the cloud admin, necessary for accessing the privileged endpoint.||Required|
|AzCredential||The credentials for the Azure Stack Hub service admin account. Use the same credentials that you used for deploying Azure Stack Hub. The script will fail if the account you use with AzCredential requires multi-factor authentication (MFA).||Required|
|VMLocalCredential||The credentials for the local admin account of the SQL resource provider VM.||Required|
|PrivilegedEndpoint||The IP address or DNS name of the privileged endpoint.||Required|
|AzureEnvironment||The Azure environment of the service admin account which you used for deploying Azure Stack Hub. Required only for Azure AD deployments. Supported environment names are AzureCloud, AzureUSGovernment, or if using a China Azure AD, AzureChinaCloud.||AzureCloud|
|DependencyFilesLocalPath||You must also put your certificate .pfx file in this directory.||Optional for single node, but mandatory for multi-node|
|DefaultSSLCertificatePassword||The password for the .pfx certificate.||Required|
|MaxRetryCount||The number of times you want to retry each operation if there's a failure.||2|
|RetryDuration||The timeout interval between retries, in seconds.||120|
|Uninstall||Removes the resource provider and all associated resources.||No|
|DebugMode||Prevents automatic cleanup on failure.||No|
Update script PowerShell example
If you are updating the SQL resource provider version to 126.96.36.199 or previous versions, you need to install specific versions of AzureRm.BootStrapper and Azure Stack Hub modules in PowerShell.
If you are updating the SQL resource provider to version 188.8.131.52 or later, you can skip this step. The deployment script will automatically download and install the necessary PowerShell modules for you to path C:\Program Files\SqlMySqlPsh.
If folder C:\Program Files\SqlMySqlPsh already exists with PowerShell module downloaded, it is recommended to clean up this folder before running the update script. This is to make sure the right version of PowerShell module is downloaded and used.
# Run the following scripts when updating to version 184.108.40.206 only. # Install the AzureRM.Bootstrapper module, set the profile, and install the AzureStack module. # Note that this might not be the most currently available version of Azure Stack Hub PowerShell. Install-Module -Name AzureRm.BootStrapper -Force Use-AzureRmProfile -Profile 2018-03-01-hybrid -Force Install-Module -Name AzureStack -RequiredVersion 1.6.0
In disconnected scenario, you need to download the required PowerShell modules and register the repository manually as a prerequisite. You can get more information in Deploy SQL resource provider
The following is an example of using the UpdateSQLProvider.ps1 script that you can run from an elevated PowerShell console. Be sure to change the variable information and passwords as needed:
# Use the NetBIOS name for the Azure Stack Hub domain. On the Azure Stack Hub SDK, the default is AzureStack but this might have been changed at installation. $domain = "AzureStack" # For integrated systems, use the IP address of one of the ERCS VMs. $privilegedEndpoint = "AzS-ERCS01" # Provide the Azure environment used for deploying Azure Stack Hub. Required only for Azure AD deployments. Supported values for the <environment name> parameter are AzureCloud, AzureChinaCloud, or AzureUSGovernment depending which Azure subscription you're using. $AzureEnvironment = "<EnvironmentName>" # Point to the directory where the resource provider installation files were extracted. $tempDir = 'C:\TEMP\SQLRP' # The service admin account (this can be Azure AD or AD FS). $serviceAdmin = "firstname.lastname@example.org" $AdminPass = ConvertTo-SecureString 'P@ssw0rd1' -AsPlainText -Force $AdminCreds = New-Object System.Management.Automation.PSCredential ($serviceAdmin, $AdminPass) # Set the credentials for the new resource provider VM. $vmLocalAdminPass = ConvertTo-SecureString 'P@ssw0rd1' -AsPlainText -Force $vmLocalAdminCreds = New-Object System.Management.Automation.PSCredential ("sqlrpadmin", $vmLocalAdminPass) # Add the cloudadmin credential required for privileged endpoint access. $CloudAdminPass = ConvertTo-SecureString 'P@ssw0rd1' -AsPlainText -Force $CloudAdminCreds = New-Object System.Management.Automation.PSCredential ("$domain\cloudadmin", $CloudAdminPass) # Change the following as appropriate. $PfxPass = ConvertTo-SecureString 'P@ssw0rd1' -AsPlainText -Force # For version 220.127.116.11 or later, the PowerShell modules used by the RP deployment are placed in C:\Program Files\SqlMySqlPsh # The deployment script adds this path to the system $env:PSModulePath to ensure correct modules are used. $rpModulePath = Join-Path -Path $env:ProgramFiles -ChildPath 'SqlMySqlPsh' $env:PSModulePath = $env:PSModulePath + ";" + $rpModulePath # Change directory to the folder where you extracted the installation files. # Then adjust the endpoints. . $tempDir\UpdateSQLProvider.ps1 -AzCredential $AdminCreds ` -VMLocalCredential $vmLocalAdminCreds ` -CloudAdminCredential $cloudAdminCreds ` -PrivilegedEndpoint $privilegedEndpoint ` -AzureEnvironment $AzureEnvironment ` -DefaultSSLCertificatePassword $PfxPass ` -DependencyFilesLocalPath $tempDir\cert
When the resource provider update script finishes, close the current PowerShell session.