Merge pull request #57857 from CarlRabeler/20181113pools

[sql db] pool max clarity

Author: rjagiewich

articles/sql-database/sql-database-resource-limits-logical-server.md

@@ -1,6 +1,6 @@
 ---
 title: Azure SQL Database resource limits - logical server | Microsoft Docs
-description: This article provides an overview of the Azure SQL Database resource limits for single databases and pooled databases using elastic pools. It also provides information regarding what happens when those resource limits are hit or exceeded.
+description: This article provides an overview of the Azure SQL Database logical server resource limits for single databases and pooled databases using elastic pools. It also provides information regarding what happens when those resource limits are hit or exceeded.
 services: sql-database
 ms.service: sql-database
 ms.subservice: 
@@ -11,9 +11,9 @@ author: CarlRabeler
 ms.author: carlrab
 ms.reviewer: sashan,moslake
 manager: craigg
-ms.date: 09/19/2018
+ms.date: 11/13/2018
 ---
-# SQL Database resource limits for single and pooled databases on a logical server 
+# SQL Database resource limits for single and pooled databases
 
 This article provides an overview of the SQL Database resource limits for single and pooled databases on a logical server. It also provides information regarding what happens when those resource limits are hit or exceeded.
 
@@ -29,18 +29,17 @@ This article provides an overview of the SQL Database resource limits for single
 | Max number of servers per subscription in any region | 200 |  
 | DTU / eDTU quota per server | 54,000 |  
 | vCore quota per server/instance | 540 |
-| Max pools per server | Limited by number of DTUs or vCores |
+| Max pools per server | Limited by number of DTUs or vCores. For example, if the each pool is 1000 DTUs, then a single server can support 54 pools.|
 ||||
 
 > [!NOTE]
-> To obtain more DTU /eDTU quota, vCore quota, or more servers than the default amount, a new support request can be submitted in the Azure portal for the subscription with issue type “Quota”. The DTU / eDTU quota and database limit per server constrains the number of elastic pools per server. 
-
+> To obtain more DTU /eDTU quota, vCore quota, or more servers than the default amount, a new support request can be submitted in the Azure portal for the subscription with issue type “Quota”. The DTU / eDTU quota and database limit per server constrains the number of elastic pools per server.
 > [!IMPORTANT]
 > As the number of databases approaches the limit per logical server, the following can occur:
-> -	Increasing latency in running queries against the master database.  This includes views of resource utilization statistics such as sys.resource_stats.
-> -	Increasing latency in management operations and rendering portal viewpoints that involve enumerating databases in the server.
+> - Increasing latency in running queries against the master database.  This includes views of resource utilization statistics such as sys.resource_stats.
+> - Increasing latency in management operations and rendering portal viewpoints that involve enumerating databases in the server.
 
-## What happens when database resource limits are reached?
+## What happens when database resource limits are reached
 
 ### Compute (DTUs and eDTUs / vCores)
 
@@ -60,11 +59,12 @@ When encountering high space utilization, mitigation options include:
 - If the database is in an elastic pool, then alternatively the database can be moved outside of the pool so that its storage space is not shared with other databases.
 - Shrink a database to reclaim unused space. For more information, see [Manage file space in Azure SQL Database](sql-database-file-space-management.md)
 
-### Sessions and workers (requests) 
+### Sessions and workers (requests)
 
-The maximum number of sessions and workers are determined by the service tier and compute size (DTUs and eDTUs). New requests are rejected when session or worker limits are reached, and clients receive an error message. While the number of connections available can be controlled by the application, the number of concurrent workers is often harder to estimate and control. This is especially true during peak load periods when database resource limits are reached and workers pile up due to longer running queries. 
+The maximum number of sessions and workers are determined by the service tier and compute size (DTUs and eDTUs). New requests are rejected when session or worker limits are reached, and clients receive an error message. While the number of connections available can be controlled by the application, the number of concurrent workers is often harder to estimate and control. This is especially true during peak load periods when database resource limits are reached and workers pile up due to longer running queries.
 
 When encountering high session or worker utilization, mitigation options include:
+
 - Increasing the service tier or compute size of the database or elastic pool. See [Scale single database resources](sql-database-single-database-scale.md) and [Scale elastic pool resources](sql-database-elastic-pool-scale.md).
 - Optimizing queries to reduce the resource utilization of each query if the cause of increased worker utilization is due to contention for compute resources. For more information, see [Query Tuning/Hinting](sql-database-performance-guidance.md#query-tuning-and-hinting).