Merge pull request #175704 from MashaMSFT/2021_tiersplit

rewrote service tier article for sql db

Author: GitHubber17

.openpublishing.redirection.azure-sql.json

@@ -179,6 +179,11 @@
             "source_path_from_root": "/articles/azure-sql/database/job-automation-managed-instances.md",
             "redirect_url": "/azure/azure-sql/managed-instance/job-automation-managed-instance",
             "redirect_document_id": true
-        }                                                                                                                        
+        },   
+        {
+            "source_path": "articles/azure-sql/database/service-tiers-general-purpose-business-critical.md",
+            "redirect_url": "/azure/azure-sql/database/service-tiers-vcore",
+            "redirect_document_id": false
+        }                                                                                                                  
     ]
 }

articles/azure-monitor/insights/azure-sql.md

@@ -2,10 +2,10 @@
 title: Azure SQL Analytics (preview) solution in Azure Monitor
 description: Azure SQL Analytics solution helps you manage your Azure SQL databases
 ms.topic: conceptual
-author: danimir
-ms.author: danil
+author: dimitri-furman
+ms.author: dfurman 
 ms.date: 11/22/2021
-ms.reviewer: wiassaf
+ms.reviewer: wiassaf, mathoma
 ms.custom: devx-track-azurepowershell
 ---
 

articles/azure-sql/database/cost-management.md

@@ -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
 
-To learn more, see [service tiers](service-tiers-general-purpose-business-critical.md). 
+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**: 
 

articles/azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -10,14 +10,16 @@ ms.subservice: service-overview
 ms.custom: sqldbrb=2, references_regions, ignite-fall-2021
 ms.devlang: 
 ms.topic: conceptual
-ms.date: 09/21/2021
+ms.date: 12/15/2021
 ---
 # What's new in Azure SQL Database?
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-This article summarizes the documentation changes associated with new features and improvements in the recent releases of [Azure SQL Database](https://azure.microsoft.com/products/azure-sql/database/). To learn more about Azure SQL Database, see the [overview](sql-database-paas-overview.md). 
+> [!div class="op_single_selector"]
+> * [Azure SQL Database](doc-changes-updates-release-notes-whats-new.md)
+> * [Azure SQL Managed Instance](../managed-instance/doc-changes-updates-release-notes-whats-new.md)
 
-For Azure SQL Managed Instance, see [What's new](../managed-instance/doc-changes-updates-release-notes-whats-new.md).
+This article summarizes the documentation changes associated with new features and improvements in the recent releases of [Azure SQL Database](https://azure.microsoft.com/products/azure-sql/database/). To learn more about Azure SQL Database, see the [overview](sql-database-paas-overview.md). 
 
 
 ## Preview 

articles/azure-sql/database/high-cpu-diagnose-troubleshoot.md

@@ -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
 

articles/azure-sql/database/index.yml

@@ -44,8 +44,6 @@ landingContent:
             url: sql-database-paas-overview.md
           - text: Purchasing options
             url: purchasing-models.md
-          - text: Service tiers
-            url: service-tiers-general-purpose-business-critical.md
           - text: Serverless compute
             url: serverless-tier-overview.md
           - text: Hyperscale service tier

articles/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](service-tiers-dtu.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.