Merge pull request #21618 from MicrosoftDocs/main

4/01 pm publish again

Author: huypub

azure-sql/index.md

@@ -1 +1,15 @@
-# Welcome to azure-sql!
+---
+title: Azure SQL documentation
+description: "Azure SQL is a family of SQL Server database engine products in the cloud, from a fully managed database in Azure SQL Database, a fully managed instance in Azure SQL Managed Instance, or SQL Server installed to virtual machine in Azure."
+services: sql-database
+ms.service: sql-db-mi
+ms.topic: landing-page
+author: MashaMSFT
+ms.author: mathoma
+ms.reviewer: kendralittle
+ms.date: 04/01/2021
+---
+
+# Azure SQL documentation
+
+See [Azure SQL](/azure/azure-sql/index).

docs/relational-databases/system-dynamic-management-views/sys-dm-workload-management-workload-group-stats-transact-sql.md

@@ -27,7 +27,7 @@ Returns workload group statistics and the effective values of the workload group
 |name|**sysname**|Name of the workload group.||
 |statistics_start_time|**datetime**|Time that statistics collection began for the workload group.  The value  is either when the workload group was created or when instance is paused or scaled.||
 |total_request_count|**bigint**|Cumulative count of completed requests in the workload group.||
-|total_shared_resource_reqeusts|**bigint**|Cumulative count of completed requests in the workload group that used resources from the shared pool.||
+|total_shared_resource_requests|**bigint**|Cumulative count of completed requests in the workload group that go beyond the reserved resources for the workload group and use resources from the shared pool. When the workload group does not have a MinResourcePercentage set, the requests will always be using shared resources and do not register in this count.||
 |total_queued_request_count|**bigint**|Cumulative count of requests queued after the max_concurrency limit was reached.||
 |total_request_execution_timeouts|**bigint**|Cumulative count of requests in the workload group that timed out before completion based on the query_execution_timeout_sec setting.||
 |effective_min_percentage_resource|**tinyint**|The effective min_percentage_resource setting allowed considering the service level and the workload group settings. The effective min_percentage_resource can be adjusted higher on lower service levels.  For example, on DW100c, the lowest min_percentage_resource allowable is 25%.  The min_percentage_resource is adjusted to 0% if the value cannot be granted at the service level.  For example, min_percentage_resource set to 10% at DW6000c, would have an effective_min_percentage_resource of 0% when scaled down to DW100c.||

docs/relational-databases/track-changes/about-change-data-capture-sql-server.md

@@ -54,11 +54,11 @@ To provide more specific performance optimization guidance to customers, more de
 
 - Monitor space utilization closely and test your workload thoroughly before enabling CDC on databases in production.
 
-- Monitor log generation rate. To learn more [here](https://docs.microsoft.com/azure/azure-sql/database/resource-limits-logical-server#resource-consumption-by-user-workloads-and-internal-processes). 
+- Monitor log generation rate. To learn more [here](/azure/azure-sql/database/resource-limits-logical-server#resource-consumption-by-user-workloads-and-internal-processes). 
 
 - Scan/cleanup are part of user workload (user’s resources are used). Performance impact can be substantial since entire rows are added to change tables and for updates operations pre-image is also included.  
 
-- Elastic Pools - Number of CDC-enabled databases should not exceed the number of vCores of the pool, in order to avoid latency increase. Learn more about resource management in dense Elastic Pools [here](https://docs.microsoft.com/azure/azure-sql/database/elastic-pool-resource-management). 
+- Elastic Pools - Number of CDC-enabled databases should not exceed the number of vCores of the pool, in order to avoid latency increase. Learn more about resource management in dense Elastic Pools [here](/azure/azure-sql/database/elastic-pool-resource-management). 
 
 - Cleanup – based on the customer's workload, it may be advised to keep the retention period smaller than the default of 3 days, to ensure that the cleanup catches up with all changes in change table. In general, it is good to keep the retention low and track the database size.