Merge pull request #49662 from jovanpop-msft/master

updated vcores resource tiers

Author: PRMerger7

articles/sql-database/sql-database-service-tiers-vcore.md

@@ -14,10 +14,10 @@ ms.author: carlrab
 # Choosing a vCore service tier, compute, memory, storage, and IO resources
 
 The vCore-based purchasing model enables you to independently scale compute and storage resources, match on-premises performance, and optimize price. It also enables you to choose generation of hardware:
-- Gen 4 - Logical CPUs are based on Intel E5-2673 v3 (Haswell) 2.4 GHz processors, vCore = 1 PP (physical core), attached SSD
-- Gen 5 - Logical CPUs are based on Intel E5-2673 v4 (Broadwell) 2.3 GHz processors, vCore=1 LP (hyper-thread), fast eNVM SSD
+- Gen 4 - Up to 24 logical CPUs based on Intel E5-2673 v3 (Haswell) 2.4 GHz processors, vCore = 1 PP (physical core), 7 GB per core, attached SSD
+- Gen 5 - Up to 80 logical CPUs based on Intel E5-2673 v4 (Broadwell) 2.3 GHz processors, vCore=1 LP (hyper-thread), 5.5. GB per core, fast eNVM SSD
 
-It also allows you to use [Azure Hybrid Use Benefit for SQL Server](../virtual-machines/windows/hybrid-use-benefit-licensing.md) to gain cost savings.
+vCore model also allows you to use [Azure Hybrid Use Benefit for SQL Server](../virtual-machines/windows/hybrid-use-benefit-licensing.md) to gain cost savings.
 
 ## Service tier characteristics
 
@@ -28,7 +28,7 @@ The following table helps you understand the differences between these two tiers
 ||**General Purpose**|**Business Critical**|
 |---|---|---|
 |Best for|Most business workloads. Offers budget oriented balanced and scalable compute and storage options.|Business applications with high IO requirements. Offers highest resilience to failures using several isolated replicas.|
-|Compute|1 to 80 vCore, Gen4\* and Gen5 |1 to 80 vCore, Gen4\* and Gen5|
+|Compute|Gen4: 1 to 24 vCore<br/>Gen5: 1 to 80 vCore|Gen4: 1 to 24 vCore<br/>Gen5: 1 to 80 vCore|
 |Memory|Gen4: 7 GB per core<br>Gen5: 5.5 GB per core | Gen4: 7 GB per core<br>Gen5: 5.5 GB per core |
 |Storage|[Premium remote storage](../virtual-machines/windows/premium-storage.md),<br/>Singleton Database: 5 GB – 4 TB<br/>Managed Instance: 32 GB - 8 TB |Local SSD storage,<br/>Single Database: 5 GB – 4 TB<br/>Managed Instance: 32 GB - 4 TB |
 |IO throughput (approximate)|Singleton Database: 500 IOPS per vCore with 7000 maximum IOPS</br>Managed Instance: Depends on [size of file](../virtual-machines/windows/premium-storage-performance.md#premium-storage-disk-sizes)|5000 IOPS per core with 200000 maximum IOPS|
@@ -37,7 +37,7 @@ The following table helps you understand the differences between these two tiers
 |In-Memory|N/A|Supported|
 |||
 
-\* Managed Instance don't supports more than 24 vCores in Gen4.
+For more information, see [vCore resource limits in Singelton Database](sql-database-vcore-resource-limits-single-databases.md) and [vCore resource limits in Managed Instance](sql-database-managed-instance.md#vcore-based-purchasing-model). 
 
 > [!IMPORTANT]
 > If you need less than one vCore of compute capacity, use the DTU-based purchasing model.
@@ -50,6 +50,7 @@ Consider the following:
 - The allocated storage is used by data files (MDF) and log files (LDF) files.
 - Each Singleton Database performance level supports a maximum database size, with a default max size of 32 GB.
 - When you configure the required Singleton database size (size of MDF), 30% of additional storage is automatically added to support LDF
+- Storage size in Managed Instance must be specified in multiples of 32 GB.
 - You can select any Singleton database size between 10 GB and the supported maximum
  - For Standard storage, increase or decrease size in 10-GB increments
  - For Premium storage, increase or decrease size in 250-GB increments