Azure Arc SQL Server is a part of Azure Arc that allows you to take advantage of Azure services in the management of your SQL Server environments in your own data center (On-Prem) or cloud environments.<\/p>\n
We said Azure Arc SQL Server is part of Azure Arc, but what is Microsoft Azure Arc?<\/p>\n
Azure Arc is currently supported in East US, East US 2, West US 2, Australia East, Southeast Asia, North Europe, West Europe, UK South. Also for using Azure Arc<\/p>\n
You need to Register the Resource Provider named in your Azure subscription.<\/p>\n
You can do the registration process through the Azure Portal or you can do it through Powershell. To do it with Powershell over Azure Cloud Shell;<\/p>\nPicture 1: Azure Cloud Shell<\/figcaption><\/figure>\n
You should run the above pieces of code one by one from Azure Cloud Shell.<\/p>\n
Operating systems supported by Azure Arc;<\/p>\n
Windows Server 2012 R2 and higher (including Windows Server Core) \nUbuntu 16.04 and 18.04 \nCentOS Linux 7 \nSUSE Linux Enterprise Server (SLES) 15 \nRed Hat Enterprise Linux (RHEL) 7 \nAmazon Linux 2<\/p>\n
Azure Arc data services aim to manage your cloud resources in a hybrid structure with the resource in-house.<\/p>\n
So, how does this happen? At this point, Microsoft is expanding its Azure Resource Manager (ARM) to include these resources.<\/p>\n
ARM made it possible to install, deploy, manage and monitor Azure resources as a single group.<\/p>\n
We can say that Azure Arc is an extended service to organize ARM on-premises or any cloud resources. Under the umbrella of Azure Arc;<\/p>\n
1. Azure Arc-Enabled Server (Azure Arc Servers) \n2. Azure-Enabled Kubernetes (Azure Arc Kubernetes) \n3. SQL Server with Azure Arc (Azure Arc SQL Server) \n4. Azure-Enabled Data Services (Azure Arc Data Services) \nyou can use.<\/p>\n
To start using Azure Arc SQL Server, we follow the Azure Arc route to All Services through the Azure Portal.<\/p>\nPicture 2: Azure Arc<\/figcaption><\/figure>\n
We select SQL Server (Preview) from the menu on the left and click the Create SQL Server \u2013 Azure Arc button in the middle of the page.<\/p>\nPicture 3: Azure Arc SQL (Preview)<\/figcaption><\/figure>\n
A screen showing the Azure Arc SQL Server requirements will meet you.<\/p>\nPicture 4: Register Azure Arc Enabled SQL Server<\/figcaption><\/figure>\n
As a requirement on the screen, a virtual or physical server running SQL Server, an account with administrative rights to apply Azure permissions, and Azure Powershell are required.<\/p>\n
Assuming that this environment is ready, we click on the Next: Server Details button at the bottom left and continue.<\/p>\n
As an environment, we have a server named DMCAZUREARCSQL that we have located on AWS and has SQL Server 2019 Standard Edition installed on it.<\/p>\n
We will also be running the powershell code blocks that are requested to be run on the following screen through this server.<\/p>\n
You see the Server Details image below. On this screen, it requests some information from us.<\/p>\nPicture 5: Azure Arc SQL Server \u2013 Server Details Ekran\u0131<\/figcaption><\/figure>\n
The first of the information on Picture-5 is the selection of the Subscription we are working with, and the second information is the resource group that it wants us to choose depending on this Subscription.<\/p>\n
Since there is no defined resource group, let’s type resource group on the search screen just above and create a new resource group from the resource group section.<\/p>\n
For our example, we created a resource group named rg-azurearcsql in West-US 2.<\/p>\n
Region information and operating system information are requested in the server details section.<\/p>\n
Currently, the region information accepted by Azure Arc SQL Server is as follows.<\/p>\nPicture 6: Region List<\/figcaption><\/figure>\n
Since the resource group we created is in West US 2 and we have selected it, West US 2 will come directly in this section.<\/p>\n
In the Operating System part, it asks us where the SQL Server, which we will include in Azure Arc, is running.<\/p>\n
You know, now SQL Server can run on Linux.<\/p>\n
For this reason, you can see Windows and Linux in the list. In our example, we choose Windows because our operating system is Windows Server 2019.<\/p>\n
In the Proxy Server part, if we are using a proxy while accessing SQL Server, it asks us to write it.<\/p>\n
Since there is no proxy in our example, we leave this field blank and move on to the next screen.<\/p>\nPicture 7: Register Azure Arc SQL Server \u2013 Information entered<\/figcaption><\/figure>\n
On the Tags screen, which is the next screen, it asks us to fill in some tag fields for this Azure Arc that we will create.<\/p>\n
Of course, this screen is not mandatory.<\/p>\npicture 8: Tags Screen<\/figcaption><\/figure>\n
When we say Run Scripts as the last step, it gives us a powershell script that contains the definitions we have given and performs some agent installation processes.<\/p>\npicture 9: Run Script Screen<\/figcaption><\/figure>\n
Either copy the codes in Picture-9 or download them and transfer them to the server you will run.<\/p>\n
We download it and transfer it to the server we want to run.<\/p>\n
When you edit the Powershell file with Windows Powershell ISE or notepad, you will see that it primarily downloads an application named AzureConnectedMachineAgent and includes us in Azure.<\/p>\n
In the following codes, you will see that there are code blocks that include installing the Azure Powershell module and extending SQL Server on Azure Arc.<\/p>\n
In our example, we are running Windows Powershell ISE and it gives us a warning screen that Azure Powershell should be installed first.<\/p>\n
Here we say Yes and allow the installation of the Azure Powershell module.<\/p>\nPicture 10: Install Azure Powershell Module<\/figcaption><\/figure>\n
During the Azure Powershell installation, it asks for your confirmation in Nuget, and after you give this confirmation, it continues the installation process.<\/p>\nPicture 11: Installing Azure Powershell Module<\/figcaption><\/figure>\n
While the installation process is in progress, it will ask you to open a page from the browser and perform a verification process.<\/p>\nPicture 12: Verification process<\/figcaption><\/figure>\n
When you go to the Device Login page, it asks you to enter a code.<\/p>\n
I enter the code seen in Picture-12 and on the next screen it asks me to choose my Microsoft Azure account that I want to process.<\/p>\n
I select my required Azure account.<\/p>\nPicture 13: Successful Verification<\/figcaption><\/figure>\n
After choosing my Azure account, my process was completed successfully as seen in picture-13.<\/p>\n
When I return to the Powershell screen, I see that my Azure Arc SQL Server Register operation was successful.<\/p>\nPicture 14: Register Azure Arc- SQL Server<\/figcaption><\/figure>\n
In line with the information seen in Picture 14, I confirm that I am now in a position to manage my server on AWS with Azure Arc from the Azure Portal, and I immediately come to the Azure Arc section through the Azure Portal and check it.<\/p>\nPicture 15: All Azure Arc Resources<\/figcaption><\/figure>\n
As you can see when registering for Azure Arc SQL Server, we have registered the server where SQL Server is running on Azure Arc.<\/p>\n
We made both Azure Arc- Server and Azure Arc SQL Server with the only registration process you can understand.<\/p>\n
So what features do they offer us? With the Azure Arc-Server facility,<\/p>\n
I can manage my virtual server located in AWS from Azure according to the image below.<\/p>\nPicture 16: Azure Arc Server – Overview<\/figcaption><\/figure>\n
As you can see in the picture above, it allows me to do many features such as Update management, Log analysis, monitoring for potential security vulnerabilities.<\/p>\n
So what’s on the Azure Arc SQL Server side?<\/p>\nPicture 17: Azure Arc SQL Server – Overview<\/figcaption><\/figure>\n
Due to the fact that Azure Arc-SQL Server is also in preview, we see that its capabilities or features are limited for now,<\/p>\n
but as it stands, it shows us that it will be a successful product as it evaluates the configuration of SQL Server’s health and monitors possible security vulnerabilities.<\/p>\n
However, it seems that it will bring a new perspective to Hybrid environments with its Microsoft Azure Arc structure,<\/p>\n
as it develops in solving difficulties such as Patch and version transitions,<\/p>\n
Manually applied DBA tasks, Scale problems experienced in OnPrem environments.<\/p>\n
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-1-1.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-2.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-3.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-4.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-5.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-6.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-7.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-8.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-9.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-10.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-11.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-12.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-13.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-14.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-15.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-16.png\")
![\"\"](\"http:\/\/www.sqlekibi.com\/wp-content\/uploads\/2021\/02\/arc-resim-17.png\")