trying to fix my sups

MashaMSFT · MashaMSFT · commit a67476fe4edc · 2020-03-25T18:16:19.000-07:00
diff --git a/articles/sql-database/sql-database-vcore-resource-limits-elastic-pools.md b/articles/sql-database/sql-database-vcore-resource-limits-elastic-pools.md
@@ -46,7 +46,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |TempDB max data size (GB)|32|64|96|128|160|192|
 |Storage type|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|
 |IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
-|Max data IOPS per pool \<sup>1<sup> |400|800|1200|1600|2000|2400|
+|Max data IOPS per pool <sup>1</sup> |400|800|1200|1600|2000|2400|
 |Max log rate per pool (MBps)|4.7|9.4|14.1|18.8|23.4|28.1|
 |Max concurrent workers per pool (requests) <sup>2<sup> |210|420|630|840|1050|1260|
 |Max concurrent logins per pool <sup>2<sup> |210|420|630|840|1050|1260|
@@ -57,7 +57,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|N/A|N/A|N/A|N/A|N/A|N/A|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 <sup>2<sup> For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
@@ -76,18 +76,18 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |TempDB max data size (GB)|224|256|288|320|512|768|
 |Storage type|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|
 |IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
-|Max data IOPS per pool \<sup>1<sup>|2800|3200|3600|4000|6400|9600|
+|Max data IOPS per pool <sup>1</sup>|2800|3200|3600|4000|6400|9600|
 |Max log rate per pool (MBps)|32.8|37.5|37.5|37.5|37.5|37.5|
-|Max concurrent workers per pool (requests) \<sup>1<sup>|1470|1680|1890|2100|3360|5040|
-|Max concurrent logins pool (requests) \<sup>1<sup>|1470|1680|1890|2100|3360|5040|
+|Max concurrent workers per pool (requests) <sup>1</sup>|1470|1680|1890|2100|3360|5040|
+|Max concurrent logins pool (requests) <sup>1</sup>|1470|1680|1890|2100|3360|5040|
 |Max concurrent sessions|30,000|30,000|30,000|30,000|30,000|30,000|
 |Min/max elastic pool vCore choices per database|0, 0.25, 0.5, 1...7|0, 0.25, 0.5, 1...8|0, 0.25, 0.5, 1...9|0, 0.25, 0.5, 1...10|0, 0.25, 0.5, 1...10, 16|0, 0.25, 0.5, 1...10, 16, 24|
 |Number of replicas|1|1|1|1|1|1|
 |Multi-AZ|N/A|N/A|N/A|N/A|N/A|N/A|
 |Read Scale-out|N/A|N/A|N/A|N/A|N/A|N/A|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-\<sup>1<sup> For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
+<sup>1</sup> For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
 ## General purpose - provisioned compute - Gen5
 
@@ -106,7 +106,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |TempDB max data size (GB)|64|128|192|256|320|384|448|
 |Storage type|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|
 |IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
-|Max data IOPS per pool \<sup>1<sup>|800|1600|2400|3200|4000|4800|5600|
+|Max data IOPS per pool \<sup>1</sup>|800|1600|2400|3200|4000|4800|5600|
 |Max log rate per pool (MBps)|9.4|18.8|28.1|37.5|37.5|37.5|37.5|
 |Max concurrent workers per pool (requests) **|210|420|630|840|1050|1260|1470|
 |Max concurrent logins per pool (requests) **|210|420|630|840|1050|1260|1470|
@@ -117,7 +117,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|N/A|N/A|N/A|N/A|N/A|N/A|N/A|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-\<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 \*\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
@@ -136,7 +136,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |TempDB max data size (GB)|512|576|640|768|1024|1280|2560|
 |Storage type|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|Premium (Remote) Storage|
 |IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
-|Max data IOPS per pool \<sup>1<sup> |6,400|7,200|8,000|9,600|12,800|16,000|32,000|
+|Max data IOPS per pool <sup>1</sup> |6,400|7,200|8,000|9,600|12,800|16,000|32,000|
 |Max log rate per pool (MBps)|37.5|37.5|37.5|37.5|37.5|37.5|37.5|
 |Max concurrent workers per pool (requests) **|1680|1890|2100|2520|3360|4200|8400|
 |Max concurrent logins per pool (requests) **|1680|1890|2100|2520|3360|4200|8400|
@@ -147,7 +147,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|N/A|N/A|N/A|N/A|N/A|N/A|N/A|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-\<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 \*\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
@@ -168,7 +168,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |TempDB max data size (GB)|333|
 |Storage type|Premium (Remote) Storage|
 |IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|
-|Max data IOPS per pool \<sup>1<sup>|16,000|
+|Max data IOPS per pool \<sup>1</sup>|16,000|
 |Max log rate per pool (MBps)|37.5|
 |Max concurrent workers per pool (requests) **|3780|
 |Max concurrent logins per pool (requests) **|3780|
@@ -179,7 +179,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|N/A|
 |Included backup storage|1X DB size|
 
-\<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+\<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 \*\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
@@ -203,7 +203,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Max log size (GB)|307|307|307|307|307|
 |TempDB max data size (GB)|64|96|128|160|192|
 |IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
-|Max data IOPS per pool \<sup>1<sup>|9,000|13,500|18,000|22,500|27,000|
+|Max data IOPS per pool \<sup>1</sup>|9,000|13,500|18,000|22,500|27,000|
 |Max log rate per pool (MBps)|20|30|40|50|60|
 |Max concurrent workers per pool (requests) **|420|630|840|1050|1260|
 |Max concurrent logins per pool (requests) **|420|630|840|1050|1260|
@@ -214,7 +214,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|Yes|Yes|Yes|Yes|Yes|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-\<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+\<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 \*\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
@@ -233,7 +233,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Max log size (GB)|307|307|307|307|307|307|
 |TempDB max data size (GB)|224|256|288|320|512|768|
 |IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
-|Max data IOPS per pool \<sup>1<sup>|31,500|36,000|40,500|45,000|72,000|96,000|
+|Max data IOPS per pool \<sup>1</sup>|31,500|36,000|40,500|45,000|72,000|96,000|
 |Max log rate per pool (MBps)|70|80|80|80|80|80|
 |Max concurrent workers per pool (requests) **|1470|1680|1890|2100|3360|5040|
 |Max concurrent logins per pool (requests) **|1470|1680|1890|2100|3360|5040|
@@ -244,7 +244,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|Yes|Yes|Yes|Yes|Yes|Yes|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-\<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+\<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 \*\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
@@ -265,7 +265,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |TempDB max data size (GB)|128|192|256|320|384|448|
 |Storage type|Local SSD|Local SSD|Local SSD|Local SSD|Local SSD|Local SSD|
 |IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
-|Max data IOPS per pool \<sup>1<sup>|18,000|27,000|36,000|45,000|54,000|63,000|
+|Max data IOPS per pool \<sup>1</sup>|18,000|27,000|36,000|45,000|54,000|63,000|
 |Max log rate per pool (MBps)|60|90|120|120|120|120|
 |Max concurrent workers per pool (requests) **|420|630|840|1050|1260|1470|
 |Max concurrent logins per pool (requests) **|420|630|840|1050|1260|1470|
@@ -276,7 +276,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 |Read Scale-out|Yes|Yes|Yes|Yes|Yes|Yes|
 |Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
 
-\<sup>1<sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
+\<sup>1</sup> The maximum value for IO sizes ranging between 8 KB and 64 KB. Actual IOPS are workload-dependent. For details, see [Data IO Governance](sql-database-resource-limits-database-server.md#resource-governance).
 
 \*\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
