fixing issues

MashaMSFT · MashaMSFT · commit c4360bb2b979 · 2021-12-01T18:10:22.000-08:00
diff --git a/azure-sql/database/migrate-dtu-to-vcore.md b/azure-sql/database/migrate-dtu-to-vcore.md
@@ -29,7 +29,7 @@ To choose the service objective, or compute size, for the migrated database in t
 > [!TIP]
 > This rule is approximate because it does not consider the hardware generation used for the DTU database or elastic pool. 
 
-In the DTU model, the system may select any available [hardware generation](purchasing-models.md#hardware-generations-in-the-dtu-based-purchasing-model) for your database or elastic pool. Further, in the DTU model you have only indirect control over the number of vCores (logical CPUs) by choosing higher or lower DTU or eDTU values. 
+In the DTU model, the system may select any available [hardware generation](purchasing-models.md#hardware-generations) for your database or elastic pool. Further, in the DTU model you have only indirect control over the number of vCores (logical CPUs) by choosing higher or lower DTU or eDTU values. 
 
 In the vCore model, customers must make an explicit choice of both the hardware generation and the number of vCores (logical CPUs). While DTU model does not offer these choices, the hardware generation and the number of logical CPUs used for every database and elastic pool are exposed via dynamic management views. This makes it possible to determine the matching vCore service objective more precisely. 
 
diff --git a/azure-sql/database/purchasing-models.md b/azure-sql/database/purchasing-models.md
@@ -60,7 +60,7 @@ The following table and chart compare and contrast the vCore-based and the DTU-b
 
 |**Purchasing model**|**Description**|**Best for**|
 |---|---|---|
-|DTU-based|This model is based on a bundled measure of compute, storage, and I/O resources. Compute sizes are expressed in DTUs for single databases and in elastic database transaction units (eDTUs) for elastic pools. For more information about DTUs and eDTUs, see [What are DTUs and eDTUs?](purchasing-models.md#dtu-based-purchasing-model).|Customers who want simple, preconfigured resource options|
+|DTU-based|This model is based on a bundled measure of compute, storage, and I/O resources. Compute sizes are expressed in DTUs for single databases and in elastic database transaction units (eDTUs) for elastic pools. For more information about DTUs and eDTUs, see [What are DTUs and eDTUs?](purchasing-models.md#dtu-purchasing-model).|Customers who want simple, preconfigured resource options|
 |vCore-based|This model allows you to independently choose compute and storage resources. The vCore-based purchasing model also allows you to use [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/) for SQL Server to save costs.|Customers who value flexibility, control, and transparency|
 ||||  
 
diff --git a/azure-sql/database/resource-limits-logical-server.md b/azure-sql/database/resource-limits-logical-server.md
@@ -209,5 +209,5 @@ Because all data is copied to local storage volumes on different machines, movin
 ## Next steps
 
 - For information about general Azure limits, see [Azure subscription and service limits, quotas, and constraints](../../azure-resource-manager/management/azure-subscription-service-limits.md).
-- For information about DTUs and eDTUs, see [DTUs and eDTUs](purchasing-models.md#dtu-based-purchasing-model).
+- For information about DTUs and eDTUs, see [DTUs and eDTUs](purchasing-models.md#dtu-purchasing-model).
 - For information about tempdb size limits, see [TempDB in Azure SQL Database](/sql/relational-databases/databases/tempdb-database#tempdb-database-in-sql-database).
diff --git a/azure-sql/database/saas-dbpertenant-performance-monitoring.md b/azure-sql/database/saas-dbpertenant-performance-monitoring.md
@@ -18,7 +18,7 @@ ms.date: 01/25/2019
 
 In this tutorial, several key performance management scenarios used in SaaS applications are explored. Using a load generator to simulate activity across all tenant databases, the built-in monitoring and alerting features of SQL Database and elastic pools are demonstrated.
 
-The Wingtip Tickets SaaS Database Per Tenant app uses a single-tenant data model, where each venue (tenant) has their own database. Like many SaaS applications, the anticipated tenant workload pattern is unpredictable and sporadic. In other words, ticket sales may occur at any time. To take advantage of this typical database usage pattern, tenant databases are deployed into elastic pools. Elastic pools optimize the cost of a solution by sharing resources across many databases. With this type of pattern, it's important to monitor database and pool resource usage to ensure that loads are reasonably balanced across pools. You also need to ensure that individual databases have adequate resources, and that pools are not hitting their [eDTU](purchasing-models.md#dtu-based-purchasing-model) limits. This tutorial explores ways to monitor and manage databases and pools, and how to take corrective action in response to variations in workload.
+The Wingtip Tickets SaaS Database Per Tenant app uses a single-tenant data model, where each venue (tenant) has their own database. Like many SaaS applications, the anticipated tenant workload pattern is unpredictable and sporadic. In other words, ticket sales may occur at any time. To take advantage of this typical database usage pattern, tenant databases are deployed into elastic pools. Elastic pools optimize the cost of a solution by sharing resources across many databases. With this type of pattern, it's important to monitor database and pool resource usage to ensure that loads are reasonably balanced across pools. You also need to ensure that individual databases have adequate resources, and that pools are not hitting their [eDTU](purchasing-models.md#dtu-purchasing-model) limits. This tutorial explores ways to monitor and manage databases and pools, and how to take corrective action in response to variations in workload.
 
 In this tutorial you learn how to:
 
diff --git a/azure-sql/database/saas-multitenantdb-performance-monitoring.md b/azure-sql/database/saas-multitenantdb-performance-monitoring.md
@@ -17,7 +17,7 @@ ms.date: 01/25/2019
 
 In this tutorial, several key performance management scenarios used in SaaS applications are explored. Using a load generator to simulate activity across sharded multi-tenant databases, the built-in monitoring and alerting features of Azure SQL Database are demonstrated.
 
-The Wingtip Tickets SaaS Multi-tenant Database app uses a sharded multi-tenant data model, where venue (tenant) data is distributed by tenant ID across potentially multiple databases. Like many SaaS applications, the anticipated tenant workload pattern is unpredictable and sporadic. In other words, ticket sales may occur at any time. To take advantage of this typical database usage pattern, databases can be scaled up and down to optimize the cost of a solution. With this type of pattern, it's important to monitor database resource usage to ensure that loads are reasonably balanced across potentially multiple databases. You also need to ensure that individual databases have adequate resources and are not hitting their [DTU](purchasing-models.md#dtu-based-purchasing-model) limits. This tutorial explores ways to monitor and manage databases, and how to take corrective action in response to variations in workload.
+The Wingtip Tickets SaaS Multi-tenant Database app uses a sharded multi-tenant data model, where venue (tenant) data is distributed by tenant ID across potentially multiple databases. Like many SaaS applications, the anticipated tenant workload pattern is unpredictable and sporadic. In other words, ticket sales may occur at any time. To take advantage of this typical database usage pattern, databases can be scaled up and down to optimize the cost of a solution. With this type of pattern, it's important to monitor database resource usage to ensure that loads are reasonably balanced across potentially multiple databases. You also need to ensure that individual databases have adequate resources and are not hitting their [DTU](purchasing-models.md#dtu-purchasing-model) limits. This tutorial explores ways to monitor and manage databases, and how to take corrective action in response to variations in workload.
 
 In this tutorial you learn how to:
 
diff --git a/azure-sql/database/service-tier-business-critical.md b/azure-sql/database/service-tier-business-critical.md
@@ -58,7 +58,7 @@ The key reasons why you should choose business critical service tier instead of
 
 The following table shows resource limits for both Azure SQL Database and Azure SQL Managed Instance in the business critical service tier. 
 
-|  | **Azure SQL Database** | **Azure SQL Managed Instance** |
+| **Category** | **Azure SQL Database** | **Azure SQL Managed Instance** |
 |:--|:--|:--|
 | **Compute size**|1 to 128 vCores  | 4, 8, 16, 24, 32, 40, 64, 80 vCores| 
 | **Storage type** |Local SSD storage|Local SSD storage | 
diff --git a/azure-sql/database/service-tier-general-purpose.md b/azure-sql/database/service-tier-general-purpose.md
@@ -47,7 +47,7 @@ The General Purpose service tier is a default service tier in Azure SQL Database
 
 The following table shows resource limits for both Azure SQL Database and Azure SQL Managed Instance in the general purpose service tier: 
 
-|  | **Azure SQL Database** | **Azure SQL Managed Instance** |
+| **Category** | **Azure SQL Database** | **Azure SQL Managed Instance** |
 |:--|:--|:--|
 | **Compute size**| 1 - 80 vCores | 4, 8, 16, 24, 32, 40, 64, 80 vCores| 
 | **Storage type** | Remote storage | Remote storage| 
diff --git a/azure-sql/glossary-terms.md b/azure-sql/glossary-terms.md
@@ -25,7 +25,7 @@ ms.date: 5/18/2021
 ||vCore-based purchasing model|[vCore-based purchasing model](database/service-tiers-sql-database-vcore.md)|
 |Deployment option |Single database|[Single databases](database/single-database-overview.md)|
 ||Elastic pool|[Elastic pool](database/elastic-pool-overview.md)|
-|Service tier|Basic, Standard, Premium, General Purpose, Hyperscale, Business Critical|For service tiers in the vCore model, see [SQL Database service tiers](database/service-tiers-sql-database-vcore.md#service-tiers). For service tiers in the DTU model, see [DTU model](database/service-tiers-dtu.md#compare-the-dtu-based-service-tiers).|
+|Service tier|Basic, Standard, Premium, General Purpose, Hyperscale, Business Critical|For service tiers in the vCore model, see [SQL Database service tiers](database/service-tiers-sql-database-vcore.md#service-tiers). For service tiers in the DTU model, see [DTU model](database/service-tiers-dtu.md#compare-service-tiers).|
 |Compute tier|Serverless compute|[Serverless compute](database/service-tiers-sql-database-vcore.md#compute-tiers)
 ||Provisioned compute|[Provisioned compute](database/service-tiers-sql-database-vcore.md#compute-tiers)
 |Compute generation|Gen5, M-series, Fsv2-series, DC-series|[Hardware generations](database/service-tiers-sql-database-vcore.md#hardware-generations)
diff --git a/azure-sql/managed-instance/resource-limits.md b/azure-sql/managed-instance/resource-limits.md
@@ -17,13 +17,13 @@ ms.date: 10/18/2021
 [!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
 > [!div class="op_single_selector"]
-> * [Azure SQL Database](database/resource-limits-vcore-single-databases.md)
-> * [Azure SQL Managed Instance](managed-instance/resource-limits.md)
+> * [Azure SQL Database](../database/resource-limits-vcore-single-databases.md)
+> * [Azure SQL Managed Instance](resource-limits.md)
 
 This article provides an overview of the technical characteristics and resource limits for Azure SQL Managed Instance, and provides information about how to request an increase to these limits.
 
 > [!NOTE]
-> For differences in supported features and T-SQL statements see [Feature differences](../database/features-comparison.md) and [T-SQL statement support](transact-sql-tsql-differences-sql-server.md). For general differences between service tiers for Azure SQL Database and SQL Managed Instance review [general purpose](service-tier-general-purpose.md) and [business critical](service-tier-business-critical.md) service tiers. 
+> For differences in supported features and T-SQL statements see [Feature differences](../database/features-comparison.md) and [T-SQL statement support](transact-sql-tsql-differences-sql-server.md). For general differences between service tiers for Azure SQL Database and SQL Managed Instance review [general purpose](../database/service-tier-general-purpose.md) and [business critical](../database/service-tier-business-critical.md) service tiers. 
 
 ## Hardware generation characteristics
 
diff --git a/azure-sql/managed-instance/service-tiers-managed-instance-vcore.md b/azure-sql/managed-instance/service-tiers-managed-instance-vcore.md
@@ -31,14 +31,14 @@ The virtual core (vCore) purchase model used by Azure SQL Managed Instance has f
 
 Service tier options in the vCore purchase model include general purpose and business critical. The service tier generally defines the storage architecture, space and I/O limits, and business continuity options related to availability and disaster recovery. For more details, review [resource limits](resource-limits.md). 
 
-||**General purpose**|**Business critical**|
+|**Category**|**General purpose**|**Business critical**|
 |---|---|---|
 |**Best for**|Most business workloads. Offers budget-oriented, balanced, and scalable compute and storage options. |Offers business applications the highest resilience to failures by using several isolated replicas, and provides the highest I/O performance.|
 |**Availability**|1 replica, no read-scale replicas|4 replicas total, 1 [read-scale replica](../database/read-scale-out.md),<br/> 2 high availability replicas (HA)|
-|**Read-only replicas**| 0 built-in <br> 0 - 4 using [geo-replication](active-geo-replication-overview.md) | 1 built-in, included in price <br> 0 - 4 using [geo-replication](active-geo-replication-overview.md) |
+|**Read-only replicas**| 0 built-in <br> 0 - 4 using [geo-replication](../database/active-geo-replication-overview.md) | 1 built-in, included in price <br> 0 - 4 using [geo-replication](../database/active-geo-replication-overview.md) |
 |**Pricing/billing**| [vCore, reserved storage, and backup storage](https://azure.microsoft.com/pricing/details/sql-database/managed/) is charged. <br/>IOPS is not charged| [vCore, reserved storage, and backup storage](https://azure.microsoft.com/pricing/details/sql-database/managed/) is charged. <br/>IOPS is not charged.
-|**Discount models**| [Reserved instances](reserved-capacity-overview.md)<br/>[Azure Hybrid Benefit](../azure-hybrid-benefit.md) (not available on dev/test subscriptions)<br/>[Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/) and [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0023p/) Dev/Test subscriptions|[Reserved instances](reserved-capacity-overview.md)<br/>[Azure Hybrid Benefit](../azure-hybrid-benefit.md) (not available on dev/test subscriptions)<br/>[Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/) and [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0023p/) Dev/Test subscriptions|
-||||
+|**Discount models**| [Reserved instances](../database/reserved-capacity-overview.md)<br/>[Azure Hybrid Benefit](../azure-hybrid-benefit.md) (not available on dev/test subscriptions)<br/>[Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/) and [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0023p/) Dev/Test subscriptions|[Reserved instances](../database/reserved-capacity-overview.md)<br/>[Azure Hybrid Benefit](../azure-hybrid-benefit.md) (not available on dev/test subscriptions)<br/>[Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/) and [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0023p/) Dev/Test subscriptions|
+|||
 
 ### Choosing a service tier
 
