Merge pull request #49191 from JulianePadrao/update-prepare-to-maintain-sql-databases-azure

Updates on prepare-to-maintain-sql-databases-azure

Author: v-ccolin

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/1-introduction.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 11/12/2023
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/2-describe-azure-data-platform-roles.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Describe Microsoft Intelligent Data Platform roles
   description: "Describe Microsoft Intelligent Data Platform roles"
-  ms.date: 11/12/2023
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/3-understand-sql-server-azure-virtual-machine.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Understand SQL Server in an Azure virtual machine
   description: "Understand SQL Server in an Azure virtual machine"
-  ms.date: 11/12/2023
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/4-design-azure-sql-database-for-cloud-native-applications.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Design Azure SQL Database for cloud-native applications
   description: "Design Azure SQL Database for cloud-native applications"
-  ms.date: 11/12/2023
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/5-explore-azure-sql-database-managed-instance.yml

@@ -1,12 +1,12 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.prepare-to-maintain-sql-databases-azure.explore-azure-sql-database-managed-instance
-title: Explore Azure SQL Database Managed Instance
+title: Explore Azure SQL Managed Instance
 metadata:
   adobe-target: true
   prefetch-feature-rollout: true
-  title: Explore Azure SQL Database Managed Instance
-  description: "Explore Azure SQL Database Managed Instance"
-  ms.date: 11/12/2023
+  title: Explore Azure SQL Managed Instance
+  description: "Explore Azure SQL Managed Instance"
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/6-knowledge-check.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 11/12/2023
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/7-summary.yml

@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 11/12/2023
+  ms.date: 2/12/2025
   author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit

learn-pr/wwl-data-ai/prepare-to-maintain-sql-databases-azure/includes/3-understand-sql-server-azure-virtual-machine.md

@@ -1,29 +1,29 @@
-A SQL Server running in an Azure virtual machine (IaaS) is equivalent to an on-premises SQL Server. You will notice that several features described for SQL Server on Azure virtual machine are applicable to all your on-premises SQL Servers.
+A SQL Server running in an Azure virtual machine (IaaS) is equivalent to an on-premises SQL Server. You'll notice that several features described for SQL Server on Azure virtual machine are applicable to all your on-premises SQL Servers.
 
-Many applications will require SQL Server running on a virtual machine. The reasons include:
+Many applications require SQL Server running on a virtual machine. The reasons include:
 
-- **General application support and incompatibility** - For applications requiring an older version of SQL Server for vendor support. In addition, some application services may have a requirement to be installed with the database instance in a manner that is not compatible with a PaaS offering.
+- **General application support and incompatibility** - For applications requiring an older version of SQL Server for vendor support. In addition, some application services may have a requirement to be installed with the database instance in a manner that isn't compatible with a PaaS offering.
 
 - **Use of other SQL Server Services** - In order to maximize licensing, many users choose to run SQL Server Analysis Services (SSAS), SQL Server Integration Services (SSIS), and/or SQL Server Reporting Services (SSRS) on the same machine as the database engine.
 
 ## Versions of SQL Server available
 
-Microsoft keeps images of all supported versions of SQL Server available in Azure Marketplace. If you have a need for an older version, that is covered by an extended support contract, you must install your own SQL Server binaries.
+Microsoft keeps images of all supported versions of SQL Server available in the Azure Marketplace. If you require an older version that is covered by an extended support contract, you'll need to install your own SQL Server binaries.
 
 ## Backup solutions
 
-In recent releases of SQL Server, Microsoft has introduced several features to support running SQL Server in an Azure virtual machine. We are going to focus on two key backup features:
+In recent releases of SQL Server, Microsoft has introduced several features to support running SQL Server in an Azure virtual machine. We're going to focus on two key backup features:
 
 - Back up to URL
 - Azure Backup
 
-Back up to URL allows you to use standard backup syntax to back up your databases to Azure Blob Storage service, while Azure Backup for SQL Server Virtual Machines offers a complete enterprise backup solution that automatically handles your backups across your infrastructure.
+The back up to URL option enables you to back up your databases to Azure Blob Storage service. Azure Backup for SQL Server Virtual Machines provides a comprehensive enterprise backup solution that automatically manages your backups across your entire infrastructure.
 
 ## Deployment options
 
-All resources in Azure share a common provider known as Azure Resource Manager that acts as a management, and deployment service for cloud services. While there are numerous ways to deploy Azure resources, ultimately, they all end up going into JSON documents known as Azure Resource Manager template, which is one of the deployment options for Azure resources.
+All resources in Azure are managed and deployed through a common provider known as Azure Resource Manager. While there are various methods to deploy Azure resources, they ultimately converge into JSON documents called Azure Resource Manager templates, which serve as one of the deployment options for Azure resources.
 
-The main difference between these processes is that Azure Resource Manager templates are a declarative deployment approach that describes the desired structure and state of the resources to be deployed, whereas the other methods can all be described as imperative, which uses procedural models to explicitly specify a process to be executed. In large-scale deployments, the declarative approach is better and should be followed.
+The key distinction between these methods is that Azure Resource Manager templates use a declarative deployment approach, which defines the desired structure and state of the resources to be deployed. In contrast, other methods are imperative, using procedural models to explicitly specify the steps to be executed. For large-scale deployments, the declarative approach is preferable and should be adopted.
 
 ## Overview of Azure storage
 
@@ -34,10 +34,18 @@ Azure offers a fully redundant object-based storage model, and there are a few t
 - Premium SSD
 - Ultra Disk
 
-For production SQL Server data and transaction log files, you should only use Premium SSD storage and Ultra Disk. With premium storage, you will see latencies in the range of 5-10 ms on a properly configured system. Alternatively, with Ultra Disk you may have sub millisecond latency but will likely see 1-2 ms workloads in the real world. You can use Standard storage for your database backups, as the performance is adequate for most backup and restore workloads.
+For production SQL Server data and transaction log files, you should only use Premium SSD storage and Ultra Disk. With premium storage, you see latencies in the range of 5-10 ms on a properly configured system. Alternatively, with Ultra Disk you may have sub millisecond latency but will likely see 1-2 ms workloads in the real world. You can use Standard storage for your database backups, as the performance is adequate for most backup and restore workloads.
 
 ## High availability in Azure
 
 The Azure platform is designed to be fault tolerant and provides quickly recovery from service disruptions and transient errors. In fact, many organizations see higher levels of availability in single virtual machines deployments than they previously experienced in their on-premises environments. Microsoft guarantees uptime of at least 99.9% for single instance Azure virtual machine, when using Premium SSD or Ultra Disk for all disks.
 
 Azure offers several features to support high availability including availability sets, availability zones, and load-balancing techniques that provide high availability by distributing incoming traffic among Virtual Machines.
+
+## SQL Server enabled by Azure Arc
+
+Azure Arc extends Azure management capabilities to SQL Server instances running outside of Azure, whether they're on-premises, in other clouds, or at the edge. By enabling SQL Server with Azure Arc, you can bring the benefits of Azure's cloud management and governance to your existing SQL Server deployments without needing to move them to Azure. This includes applying consistent policies, ensuring compliance, and using Azure services such as Azure Monitor and Azure Security Center for enhanced security and performance monitoring.
+
+With Azure Arc, you can centrally manage and monitor your SQL Server instances through the Azure portal just like you would with native Azure services. This unified management experience simplifies operations and reduces the complexity of managing disparate environments. Additionally, Azure Arc enables advanced features like automated updates, backup and restore, and disaster recovery for your SQL Server instances, ensuring they're always up-to-date, secure, and resilient against failures. By connecting your SQL Server instances to Azure Arc, you can also take advantage of Azure's machine learning and artificial intelligence capabilities, enabling you to build and deploy intelligent applications that use your existing data.
+
+To learn more about enabling SQL Server with Azure Arc, see [SQL Server enabled by Azure Arc](/sql/sql-server/azure-arc/overview).