debuglevel
diff --git a/‎azure-sql/database/cost-management.md‎
Lines changed: 3 additions & 1 deletion b/‎azure-sql/database/cost-management.md‎
Lines changed: 3 additions & 1 deletion
diff --git a/‎azure-sql/database/high-cpu-diagnose-troubleshoot.md‎
Lines changed: 3 additions & 3 deletions b/‎azure-sql/database/high-cpu-diagnose-troubleshoot.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎azure-sql/database/purchasing-models.md‎
Lines changed: 9 additions & 12 deletions b/‎azure-sql/database/purchasing-models.md‎
Lines changed: 9 additions & 12 deletions
diff --git a/‎azure-sql/database/resource-limits-dtu-single-databases.md‎
Lines changed: 1 addition & 1 deletion b/‎azure-sql/database/resource-limits-dtu-single-databases.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎azure-sql/database/resource-limits-logical-server.md‎
Lines changed: 9 additions & 5 deletions b/‎azure-sql/database/resource-limits-logical-server.md‎
Lines changed: 9 additions & 5 deletions
@@ -6,6 +6,7 @@ ms.author: kendralittle
 ms.custom: subject-cost-optimization
 ms.service: sql-database
 ms.subservice: service-overview
+ms.reviewer: mathoma
 ms.topic: how-to
 ms.date: 06/30/2021
 ---
@@ -70,7 +71,8 @@ Billing depends on the SKU of your product, the generation hardware of your SKU,
 - And for storage: geo-redundant storage (GRS), locally redundant storage (LRS), and zone-redundant storage (ZRS)
 - It's also possible to have a deprecated SKU from deprecated resource offerings
 
-For more information, see [purchasing models](purchasing-models.md). For more information on service tiers, see [DTU service tiers](service-tiers-dtu.md#compare-service-tiers) and [vCore service tiers](service-tiers-sql-database-vcore.md#service-tiers).
+For more information, see [vCore-based purchasing model](service-tiers-vcore.md), [DTU-based purchasing model](service-tiers-dtu.md), or [compare purchasing models](purchasing-models.md). 
+
 
 The following table shows the most common billing meters and their possible SKUs for **single databases**: 
 
 
@@ -29,7 +29,7 @@ You can quickly identify the vCore count for a database in the Azure portal if y
 
 For databases in the [serverless](serverless-tier-overview.md) compute tier, vCore count will always be equivalent to the max vCore setting for the database. VCore count will show in the **pricing tier** listed for the database on its **Overview** page. For example, a database's pricing tier might be 'General Purpose: Serverless, Gen5, 16 vCores'.
 
-If you're using a database under the [DTU-based purchase model](service-tiers-dtu.md), you will need to use Transact-SQL to query the database's vCore count.
+If you're using a database under the [DTU-based purchasing model](service-tiers-dtu.md), you will need to use Transact-SQL to query the database's vCore count.
 
 ### Identify vCore count with Transact-SQL
 
@@ -374,9 +374,9 @@ Consider experimenting with small changes in the MAXDOP configuration at the dat
 
 You may find that your workload's queries and indexes are properly tuned, or that performance tuning requires changes that you cannot make in the short term due to internal processes or other reasons. Adding more CPU resources may be beneficial for these databases. You can [scale database resources with minimal downtime](scale-resources.md).
 
-You can add more CPU resources to your Azure SQL Database by configuring the vCore count or the [hardware generation](service-tiers-sql-database-vcore.md#hardware-generations) for databases using the [vCore purchase model](service-tiers-sql-database-vcore.md).
+You can add more CPU resources to your Azure SQL Database by configuring the vCore count or the [hardware generation](service-tiers-sql-database-vcore.md#hardware-generations) for databases using the [vCore purchasing model](service-tiers-sql-database-vcore.md).
 
-Under the [DTU-based purchase model](service-tiers-dtu.md), you can raise your service tier and increase the number of database transaction units (DTUs). A DTU represents a blended measure of CPU, memory, reads, and writes.  One benefit of the vCore purchase model is that it allows more granular control over the hardware in use and the number of vCores. You can [migrate Azure SQL Database from the DTU-based model to the vCore-based model](migrate-dtu-to-vcore.md) to transition between purchase models.
+Under the [DTU-based purchasing model](service-tiers-dtu.md), you can raise your service tier and increase the number of database transaction units (DTUs). A DTU represents a blended measure of CPU, memory, reads, and writes.  One benefit of the vCore purchasing model is that it allows more granular control over the hardware in use and the number of vCores. You can [migrate Azure SQL Database from the DTU-based model to the vCore-based model](migrate-dtu-to-vcore.md) to transition between purchasing models.
 
 ## Next steps
 
 
@@ -1,7 +1,7 @@
 ---
 title: Purchasing models
 titleSuffix: Azure SQL Database 
-description: Learn about the purchasing models that are available for Azure SQL Database: the vCore purchasing model and the DTU purchasing model.  
+description: "Learn about the purchasing models that are available for Azure SQL Database: the vCore purchasing model and the DTU purchasing model."
 services: sql-database
 ms.service: sql-database
 ms.subservice: service-overview
@@ -11,20 +11,21 @@ ms.topic: conceptual
 author: LitKnd
 ms.author: kendralittle
 ms.reviewer: mathoma
-ms.date: 12/15/2021
+ms.date: 01/20/2022
 ---
-# Compare vCore and DTU purchasing models of Azure SQL Database
+# Compare vCore and DTU-based purchasing models of Azure SQL Database
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
 Azure SQL Database lets you easily purchase a fully managed platform as a service (PaaS) database engine that fits your performance and cost needs. Depending on the deployment model you've chosen for Azure SQL Database, you can select the purchasing model that works for you:
 
-- [Virtual core (vCore)-based purchasing model](service-tiers-sql-database-vcore.md) (recommended). This purchasing model provides a choice between a provisioned compute tier and a serverless compute tier. With the provisioned compute tier, you choose the exact amount of compute resources that are always provisioned for your workload. With the serverless compute tier, you specify the autoscaling of the compute resources over a configurable compute range. The serverless compute tier automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns. The vCore unit price per unit of time is lower in the provisioned compute tier than it is in the serverless compute tier. The [Hyperscale service tier](service-tier-hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
+- [Virtual core (vCore)-based purchasing model](service-tiers-sql-database-vcore.md) (recommended). This purchasing model provides a choice between a provisioned compute tier and a serverless compute tier. With the provisioned compute tier, you choose the exact amount of compute resources that are always provisioned for your workload. With the serverless compute tier, you specify the autoscaling of the compute resources over a configurable compute range. The serverless compute tier automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns. The vCore unit price per unit of time is lower in the provisioned compute tier than it is in the serverless compute tier. The [hyperscale service tier](service-tier-hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
 - [Database transaction unit (DTU)-based purchasing model](service-tiers-dtu.md). This purchasing model provides bundled compute and storage packages balanced for common workloads.
 
 ## vCore purchasing model
+
 There are two purchasing models:
 
-- [vCore-based purchasing model](service-tiers-vcore.md) is available for both [Azure SQL Database](sql-database-paas-overview.md) and [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md). The [Hyperscale service tier](service-tier-hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
+- [vCore-based purchasing model](service-tiers-vcore.md) is available for both [Azure SQL Database](sql-database-paas-overview.md) and [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md). The [hyperscale service tier](service-tier-hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
 - [DTU-based purchasing model](service-tiers-dtu.md) is available for [Azure SQL Database](single-database-manage.md).
 
 The following table and chart compare and contrast the vCore-based and the DTU-based purchasing models:
@@ -37,10 +38,6 @@ The following table and chart compare and contrast the vCore-based and the DTU-b
 
 ![Pricing model comparison](./media/purchasing-models/pricing-model.png)
 
-Want to optimize and save on your cloud spending?
-
-[!INCLUDE [cost-management-horizontal](../../../includes/cost-management-horizontal.md)]
-
 ## Compute costs
 
 ### Provisioned compute costs
@@ -67,16 +64,16 @@ For more information about storage prices, see the [pricing](https://azure.micro
 
 A virtual core (vCore) represents a logical CPU and offers you the option to choose between generations of hardware and the physical characteristics of the hardware (for example, the number of cores, the memory, and the storage size). The vCore-based purchasing model gives you flexibility, control, transparency of individual resource consumption, and a straightforward way to translate on-premises workload requirements to the cloud. This model allows you to choose compute, memory, and storage resources based on your workload needs.
 
-In the vCore-based purchasing model for SQL Database, you can choose between the general purpose and business critical service tiers. Review [service tiers](service-tiers-sql-database-vcore.md#service-tiers) to learn more.  For single databases, you can also choose the [Hyperscale service tier](service-tier-hyperscale.md).
+In the vCore-based purchasing model for SQL Database, you can choose between the general purpose and business critical service tiers. Review [service tiers](service-tiers-sql-database-vcore.md#service-tiers) to learn more.  For single databases, you can also choose the [hyperscale service tier](service-tier-hyperscale.md).
 
 The vCore-based purchasing model lets you independently choose compute and storage resources, match on-premises performance, and optimize price. In the vCore-based purchasing model, you pay for:
 
 - Compute resources (the service tier + the number of vCores and the amount of memory + the generation of hardware).
 - The type and amount of data and log storage.
-- Backup storage (RA-GRS).
+- Backup storage.
 
 > [!IMPORTANT]
-> Compute resources, I/O, and data and log storage are charged per database or elastic pool. Backup storage is charged per each database.
+> For single databases, compute resources, I/O, and data and log storage are charged per database. For elastic pools, these resources are charged per pool. However, backup storage is always charged per database.
 
 
 ## DTU purchasing model
 
@@ -10,7 +10,7 @@ ms.topic: reference
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: kendralittle, mathoma
-ms.date: 04/16/2021
+ms.date: 01/20/2022
 ---
 # Resource limits for single databases using the DTU purchasing model - Azure SQL Database
 
 
@@ -10,7 +10,7 @@ ms.topic: reference
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: kendralittle, mathoma
-ms.date: 10/01/2021
+ms.date: 01/20/2022
 ---
 
 # Resource management in Azure SQL Database
@@ -167,7 +167,7 @@ Log rate governor traffic shaping is surfaced via the following wait types (expo
 
 When encountering a log rate limit that is hampering desired scalability, consider the following options:
 
-- Scale up to a higher service level in order to get the maximum log rate of a service tier, or switch to a different service tier. The [Hyperscale](service-tier-hyperscale.md) service tier provides 100 MB/s log rate regardless of chosen service level.
+- Scale up to a higher service level in order to get the maximum log rate of a service tier, or switch to a different service tier. The [hyperscale](service-tier-hyperscale.md) service tier provides 100 MB/s log rate regardless of chosen service level.
 - If data being loaded is transient, such as staging data in an ETL process, it can be loaded into tempdb (which is minimally logged).
 - For analytic scenarios, load into a clustered [columnstore](/sql/relational-databases/indexes/columnstore-indexes-overview) table, or a table with indexes that use [data compression](/sql/relational-databases/data-compression/data-compression). This reduces the required log rate. This technique does increase CPU utilization and is only applicable to data sets that benefit from clustered columnstore indexes or data compression.
 
@@ -206,14 +206,18 @@ This move occurs in an online fashion, similarly to a database scaling operation
 Because all data is copied to local storage volumes on different machines, moving larger databases may require a substantial amount of time. During that time, if local space consumption by the database or elastic pool, or by the tempdb database grows rapidly, the risk of running out of space increases. The system initiates database movement in a balanced fashion to minimize out-of-space errors while avoiding unnecessary failovers.
 
 > [!NOTE]
-> Database movement due to insufficient local storage only occurs in the Premium or Business Critical service tiers. It does not occur in the Hyperscale, General Purpose, Standard, and Basic service tiers, because in those tiers data files are not stored in local storage.
+> Database movement due to insufficient local storage only occurs in the Premium or Business Critical service tiers. It does not occur in the hyperscale, General Purpose, Standard, and Basic service tiers, because in those tiers data files are not stored in local storage.
 
 ## Tempdb sizes
 
-Size limits for tempdb in Azure SQL Database depend on the purchasing and deployment model. To learn more, review tempdb size limits for [vCore](resource-limits-vcore-single-databases.md), [single databases (DTU)](resource-limits-dtu-single-databases.md#tempdb-sizes), [pooled databases (DTU)](resource-limits-dtu-elastic-pools.md#tempdb-sizes). 
+Size limits for tempdb in Azure SQL Database depend on the purchasing and deployment model. 
+
+To learn more, review tempdb size limits for: 
+- vCore purchasing model: [single databases](resource-limits-vcore-single-databases.md), [pooled databases](resource-limits-vcore-elastic-pools.md)
+- DTU purchasing model: [single databases](resource-limits-dtu-single-databases.md#tempdb-sizes),  [pooled databases](resource-limits-dtu-elastic-pools.md#tempdb-sizes). 
 
 ## 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-purchasing-model).
-- For information about tempdb size limits, see [vCore](resource-limits-vcore-single-databases.md), [single databases (DTU)](resource-limits-dtu-single-databases.md#tempdb-sizes), [pooled databases (DTU)](resource-limits-dtu-elastic-pools.md#tempdb-sizes).
+- For information about tempdb size limits, see [single vCore databases](resource-limits-vcore-single-databases.md), [pooled vCore databases](resource-limits-vcore-elastic-pools.md), [single DTU databases](resource-limits-dtu-single-databases.md#tempdb-sizes), and [pooled DTU databases](resource-limits-dtu-elastic-pools.md#tempdb-sizes).