Merge pull request #30443 from MicrosoftDocs/main

4/22/2024 PM Publish

Author: Albertyang0

azure-sql/database/ai-artificial-intelligence-intelligent-applications.md

@@ -17,6 +17,10 @@ This article provides an overview of using artificial intelligence (AI) options,
 
 For samples and examples, please visit the [SQL AI Samples repository](https://aka.ms/sqlaisamples).
 
+Watch this video in the [Azure SQL Database essentials series](/shows/azure-sql-database-essentials/) for a brief overview of building an AI ready application:  
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=466d4554-4747-45dd-8f21-5ae73b1fa981]
+
+
 ## Overview
 
 Large language models (LLMs) enable developers to create AI-powered applications with a familiar user experience.

azure-sql/database/connect-query-content-reference-guide.md

@@ -18,6 +18,9 @@ monikerRange: "=azuresql || =azuresql-db || =azuresql-mi"
 
 The following document includes links to Azure examples showing how to connect and query Azure SQL Database and Azure SQL Managed Instance. For some related recommendations for Transport Level Security, see [TLS considerations for database connectivity](#tls-considerations-for-database-connectivity).
 
+Watch this video in the [Azure SQL Database essentials series](/shows/azure-sql-database-essentials/) for a brief connect and query overview: 
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=c2edd421-da6b-4598-a142-5980e4f38de9]
+
 ## Quickstarts
 
 | Quickstart | Description |

azure-sql/database/index.yml

@@ -36,8 +36,10 @@ landingContent:
             url: firewall-create-server-level-portal-quickstart.md
       - linkListType: video
         links:
-          - text: Azure SQL Database overview
-            url: /shows/Azure-SQL-for-Beginners/Azure-SQL-Database-Overview-7-of-61
+          - text: Azure SQL for beginners 
+            url: /shows/Azure-SQL-for-Beginners/
+          - text: Azure SQL Database essentials
+            url: /shows/azure-sql-database-essentials/
       - linkListType: concept
         links:
           - text: What is SQL Database?

azure-sql/database/resource-limits-vcore-elastic-pools.md

@@ -569,6 +569,8 @@ The following table covers these SLOs: `BC_DC_14`, `BC_DC_16`, `BC_DC_18`, `BC_D
 
 ## Hyperscale - provisioned compute - standard-series (Gen5)
 
+Although the published Hyperscale resource limits for standard-series and premium-series are the same, premium-series offers faster CPU performance compared to standard-series, and scales up to 128 vCores, compared to 80 vCores for standard-series. Resources using premium-series are guaranteed to run on hardware with newer CPUs. Standard-series does not provide this guarantee and, depending on availability, resources may be placed on older hardware. There is no price difference between the two, but premium-series may not be available in all regions.
+
 > [!NOTE]
 > Elastic pools for Hyperscale databases are currently in preview.
 

azure-sql/database/resource-limits-vcore-single-databases.md

@@ -401,6 +401,8 @@ The following table covers these SLOs: `HS_DC_14`, `HS_DC_16`, `HS_DC_18`, `HS_D
 
 ## Hyperscale - provisioned compute - premium-series
 
+Although the published Hyperscale resource limits for standard-series and premium-series are the same, premium-series offers faster CPU performance compared to standard-series, and scales up to 128 vCores, compared to 80 vCores for standard-series. Resources using premium-series are guaranteed to run on hardware with newer CPUs. Standard-series does not provide this guarantee and, depending on availability, resources may be placed on older hardware. There is no price difference between the two, but premium-series may not be available in all regions.
+
 ### Hyperscale premium-series (part 1 of 3)
 
 Compute sizes (service level objectives, or SLOs) for Hyperscale premium-series databases follow the naming convention `HS_PRMS_` followed by the number of vCores. 

azure-sql/database/single-database-create-quickstart.md

@@ -18,6 +18,11 @@ ms.custom:
 
 In this quickstart, you create a [single database](single-database-overview.md) in Azure SQL Database using either the Azure portal, a PowerShell script, or an Azure CLI script. You then query the database using **Query editor** in the Azure portal.
 
+
+Watch this video in the [Azure SQL Database essentials series](/shows/azure-sql-database-essentials/) for an overview of the deployment process: 
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=0c5d0700-b422-4a46-99bd-84c09ba65804]
+
+
 ## Prerequisites
 
 - An active Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/).

azure-sql/database/sql-database-paas-overview.md

@@ -88,6 +88,10 @@ You can build your first app on a small, single database at a low cost per month
 - Use scripts to schedule or automate scalability for a single database. For an example, see [Use PowerShell to monitor and scale a single database](scripts/monitor-and-scale-database-powershell.md).
 - Use [elastic pools](#elastic-pools-to-maximize-resource-utilization), which allow databases to share resources in a pool based on individual database needs. [Elastic pools can also be scaled with custom scripts](scripts/monitor-and-scale-pool-powershell.md), allowing you to schedule or automate scalability.
 
+Watch this video in the [Azure SQL Database essentials series](/shows/azure-sql-database-essentials/) for a brief overview of scaling your database:  
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=e10562ba-2079-48c9-abc7-b3163c079341]
+
+
 ### Elastic pools to maximize resource utilization
 
 For many businesses and applications, being able to create single databases and dial performance up or down on demand is enough, especially if usage patterns are relatively predictable. Unpredictable usage patterns can make it hard to manage costs and your business model. [Elastic pools](elastic-pool-overview.md) are designed to solve this problem. You allocate performance resources to a pool rather than an individual database. You pay for the collective performance resources of the pool rather than for single database performance.

azure-sql/includes/failover-group-overview.md

@@ -57,6 +57,6 @@ Set the failover policy to Microsoft managed only when:
 - It's acceptable that all databases within the failover group fail over, regardless of their zone redundancy configuration or availability status. Although databases configured for zone redundancy are resilient to zonal failures and might not be impacted by an outage, they'll still be failed over if they're part of a failover group with a Microsoft managed failover policy.  
 - It's acceptable to have forced failovers of databases in the failover group without taking into consideration the application's dependency on other Azure services or components used by the application, which can cause performance degradation or unavailability of the application.
 - It's acceptable to incur an unknown amount of data loss, as the exact time of forced failover can't be controlled, and ignores the synchronization status of the secondary databases.
-- All the primary and secondary database(s) in the failover group have the same service tier, compute tier (provisioned or serverless) & compute size (DTUs or vCores). If the service level objective (SLO) of all the databases in a failover group don't match, then the failover policy will be eventually updated from Microsoft Managed to Customer Managed by Azure SQL service. 
+- All the primary and secondary database(s) in the failover group and any geo replciation relationships have the same service tier, compute tier (provisioned or serverless) & compute size (DTUs or vCores). If the service level objective (SLO) of all the databases don't match, then the failover policy will be eventually updated from Microsoft Managed to Customer Managed by Azure SQL service. 
 
 When a failover is triggered by Microsoft, an entry for the operation name **Failover Azure SQL failover group** is added to the [Azure Monitor activity log](/azure/azure-monitor/essentials/activity-log). The entry includes the name of the failover group under **Resource**, and **Event initiated by** displays a single hyphen (-) to indicate the failover was initiated by Microsoft.  This information can also be found on the **Activity log** page of the new primary server or instance in the Azure portal. 

azure-sql/index.yml

@@ -42,8 +42,10 @@ landingContent:
             url: database/firewall-create-server-level-portal-quickstart.md  
       - linkListType: video
         links:
-          - text: Azure SQL Database overview
-            url: /shows/Azure-SQL-for-Beginners/Azure-SQL-Database-Overview-7-of-61
+          - text: Azure SQL for beginners
+            url: /shows/Azure-SQL-for-Beginners/
+          - text: Azure SQL Database essentials
+            url: /shows/azure-sql-database-essentials/
       - linkListType: concept
         links:
           - text: Advanced security

azure-sql/managed-instance/managed-instance-link-feature-overview.md

@@ -18,8 +18,6 @@ ms.custom: ignite-2023
 
 This article provides an overview of the Managed Instance link feature, which enables near real-time data replication between SQL Server and Azure SQL Managed Instance. The link provides hybrid flexibility and database mobility as it unlocks several scenarios, such as scaling read-only workloads, offloading analytics and reporting to Azure, and migrating to Azure. And, with SQL Server 2022, the link enables online disaster recovery with fail back to SQL Server (currently in preview), as well as configuring the link from SQL Managed Instance to SQL Server 2022 (also in preview). 
 
-If you have product improvement suggestions or comments, or you want to report issues, contact the product group through [Managed Instance link user feedback](https://aka.ms/mi-link-feedback).
-
 ## Overview
 
 The Managed Instance link uses [distributed availability groups](/sql/database-engine/availability-groups/windows/distributed-availability-groups) to extend your data estate in a safe and secure manner, replicating data in near real-time from SQL Server hosted anywhere to Azure SQL Managed Instance, or from Azure SQL Managed Instance to SQL Server 2022 hosted anywhere.