github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity

Delete registry.md

Browse Source
This commit is contained in:
Pedro Lopes
2020-01-08 13:45:02 -08:00
committed by GitHub
parent 8cd9dc3c04
commit 109438075d
1 changed files with 0 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files
samples/manage/sql-server-extended-security-updates/registry.md
-54
View File
@@ -1,54 +0,0 @@
![](./media/solutions-microsoft-logo-small.png)
# Create the SQL Server Registry
Before being able access the Extended Security Updates (ESU) download area in the Azure portal, the SQL Server instances covered by ESUs must be registered. This ensures that you are able to download an ESU package if and when available.
**Important**: It's not required to register a SQL Server instance for ESUs when running an Azure Virtual Machine that is configured for Automatic Updates. For more information, see [Manage Windows updates by using Azure Automation](https://docs.microsoft.com/azure/automation/automation-tutorial-update-management).
## <a name="Reg"></a> Prepare to register SQL Server instances
To register SQL Server instances, you must first create a SQL Server Registry in the [Azure portal](https://portal.azure.com/#create/Microsoft.SqlServerRegistration).
**Note**: This operation only needs to be done once. After a SQL Server Registry is created, it can be used to register multiple SQL Server instances.
### Steps
1. Open the [Azure portal](https://portal.azure.com) and log in.
2. If this is your first time registering a SQL Server instance, click the plus (+) sign in the top-left area of the page to create a new resource. Then type *SQL Server Registry* in the text box and hit the **Enter** key.
![New Registry Step 1](./media/NewRegistry-Step1.png "New Registry Step 1")
3. The SQL Server Registry resource should be available. Click on it begin the Registry setup process.
![New Registry Step 2](./media/NewRegistry-Step2.png "New Registry Step 2")
4. After selecting the SQL Server Registry resource, click on the *Create* button.
![New Registry Step 3](./media/NewRegistry-Step3.png "New Registry Step 3")
5. In the **PROJECT DETAILS** section, select the ***subscription*** on which to create the Registry. Then, select either an existing ***Resource group***, or create a new one.
![New Registry Step 4](./media/NewRegistry-Step4.png "New Registry Step 4")
In the **SERVICE DETAILS** section, enter a name for the ***SQL Server registry***, and select a ***Region*** on which to deploy this new resource.
![New Registry Step 5](./media/NewRegistry-Step5.png "New Registry Step 5")
And then click on the ***Review + create*** button.
6. If the validation passed, you are presented with a screen that summarizes the choices for the new registry resource. If everything seems correct, click on the ***Create*** button to start deployment of the new resource.
![New Registry Step 6](./media/NewRegistry-Step6.png "New Registry Step 6")
Note the [Terms of Use](https://go.microsoft.com/fwlink/?linkid=2045708) and [Privacy Policy](https://go.microsoft.com/fwlink/?linkid=512132) for the SQL Server Registry are available in this window.
7. Once deployment is complete, click on the ***Go to resource*** button.
![New Registry Step 7](./media/NewRegistry-Step7.png "New Registry Step 7")
![New Registry Step 8](./media/NewRegistry-Step8.png "New Registry Step 8")
8. Now the **SQL Server Registry** is available.
![New Registry Step 9](./media/NewRegistry-Step9.png "New Registry Step 9")
To start registering SQL Server instances, see [Registering SQL Server instances](./register.md).