can't decide on a name

Author: MashaMSFT

articles/azure-sql/database/dtu-service-tiers.md

@@ -73,7 +73,7 @@ Compute sizes are expressed in terms of Database Transaction Units (DTUs) for si
 |||||
 
 > [!IMPORTANT]
-> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB.  For more information, see [P11-P15 current limitations](scale-single-database.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).  
+> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB.  For more information, see [P11-P15 current limitations](single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).  
 > [!IMPORTANT]
 > Under some circumstances, you may need to shrink a database to reclaim unused space. For more information, see [manage file space in Azure SQL Database](file-space-manage.md).
 

articles/azure-sql/database/resource-limits-dtu-elastic-pools.md

@@ -132,7 +132,7 @@ For Azure SQL Database elastic pools, the following tables show the resources av
 <sup>2</sup> For the max concurrent workers (requests) for any individual database, see [Single database resource limits](resource-limits-vcore-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.
 
 > [!IMPORTANT]
-> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB.  For more information, see [P11-P15 current limitations](scale-single-database.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).
+> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB.  For more information, see [P11-P15 current limitations](single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).
 
 If all DTUs of an elastic pool are used, then each database in the pool receives an equal amount of resources to process queries. The SQL Database service provides resource sharing fairness between databases by ensuring equal slices of compute time. Elastic pool resource sharing fairness is in addition to any amount of resource otherwise guaranteed to each database when the DTU min per database is set to a non-zero value.
 

articles/azure-sql/database/resource-limits-dtu-single-databases.md

@@ -23,7 +23,7 @@ For DTU purchasing model resource limits for elastic pools, see [DTU resource li
 The following tables show the resources available for a single database at each service tier and compute size. You can set the service tier, compute size, and storage amount for a single database using the [Azure portal](single-databases-manage.md#azure-portal), [Transact-SQL](single-databases-manage.md#transact-sql-t-sql), [PowerShell](single-databases-manage.md#powershell), the [Azure CLI](single-databases-manage.md#azure-cli), or the [REST API](single-databases-manage.md#rest-api).
 
 > [!IMPORTANT]
-> For scaling guidance and considerations, see [Scale a single database](scale-single-database.md)
+> For scaling guidance and considerations, see [Scale a single database](single-database-scale.md)
 
 ### Basic service tier
 
@@ -88,7 +88,7 @@ The following tables show the resources available for a single database at each
 \* From 1024 GB up to 4096 GB in increments of 256 GB
 
 > [!IMPORTANT]
-> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB.  For more information, see [P11-P15 current limitations](scale-single-database.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).  
+> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB.  For more information, see [P11-P15 current limitations](single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).  
 > [!NOTE]
 > For `tempdb` limits, see [tempdb limits](https://docs.microsoft.com/sql/relational-databases/databases/tempdb-database?view=sql-server-2017#tempdb-database-in-sql-database).
 

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

@@ -52,7 +52,7 @@ For single databases resource storage sizes, refer to either [DTU-based resource
 When database compute utilization (measured by DTUs and eDTUs, or vCores) becomes high, query latency increases, and queries can even time out. Under these conditions, queries may be queued by the service and are provided resources for execution as resources become free.
 When encountering high compute utilization, mitigation options include:
 
-- Increasing the compute size of the database or elastic pool to provide the database with more compute resources. See [Scale single database resources](scale-single-database.md) and [Scale elastic pool resources](elastic-pool-scale.md).
+- Increasing the compute size of the database or elastic pool to provide the database with more compute resources. See [Scale single database resources](single-database-scale.md) and [Scale elastic pool resources](elastic-pool-scale.md).
 - Optimizing queries to reduce resource utilization of each query. For more information, see [Query Tuning/Hinting](../../sql-database/sql-database-performance-guidance.md#query-tuning-and-hinting).
 
 ### Storage
@@ -61,7 +61,7 @@ When database space used reaches the max size limit, database inserts and update
 
 When encountering high space utilization, mitigation options include:
 
-- Increasing the max size of the database or elastic pool, or adding more storage. See [Scale single database resources](scale-single-database.md) and [Scale elastic pool resources](elastic-pool-scale.md).
+- Increasing the max size of the database or elastic pool, or adding more storage. See [Scale single database resources](single-database-scale.md) and [Scale elastic pool resources](elastic-pool-scale.md).
 - 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](file-space-manage.md)
 
@@ -71,7 +71,7 @@ The maximum numbers of sessions and workers are determined by the service tier a
 
 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](scale-single-database.md) and [Scale elastic pool resources](elastic-pool-scale.md).
+- Increasing the service tier or compute size of the database or elastic pool. See [Scale single database resources](single-database-scale.md) and [Scale elastic pool resources](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/sql-database-performance-guidance.md#query-tuning-and-hinting).
 - Reducing the [MAXDOP](https://docs.microsoft.com/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option#Guidelines) (maximum degree of parallelism) setting.
 - Optimizing query workload to reduce number of occurrences and duration of query blocking.

articles/azure-sql/database/resource-limits-vcore-single-databases.md

@@ -21,7 +21,7 @@ For DTU purchasing model limits for single databases on a server, see [Overview
 You can set the service tier, compute size, and storage amount for a single database using the [Azure portal](single-databases-manage.md#azure-portal), [Transact-SQL](single-databases-manage.md#transact-sql-t-sql), [PowerShell](single-databases-manage.md#powershell), the [Azure CLI](single-databases-manage.md#azure-cli), or the [REST API](single-databases-manage.md#rest-api).
 
 > [!IMPORTANT]
-> For scaling guidance and considerations, see [Scale a single database](scale-single-database.md).
+> For scaling guidance and considerations, see [Scale a single database](single-database-scale.md).
 
 ## General purpose - serverless compute - Gen5
 

articles/azure-sql/database/scale-single-database.md

@@ -75,11 +75,11 @@ A service tier change or compute rescaling operation can be canceled.
 
 In the database overview blade, navigate to **Notifications** and click on the tile indicating there is an ongoing operation:
 
-![Ongoing operation](./media/scale-single-database/ongoing-operations.png)
+![Ongoing operation](./media/single-database-scale/ongoing-operations.png)
 
 Next, click on the button labeled **Cancel this operation**.
 
-![Cancel ongoing operation](./media/scale-single-database/cancel-ongoing-operation.png)
+![Cancel ongoing operation](./media/single-database-scale/cancel-ongoing-operation.png)
 
 ### PowerShell
 

articles/azure-sql/database/single-database-overview.md

@@ -24,7 +24,7 @@ The single database deployment option creates a database in Azure SQL Database w
 
 ## Dynamic scalability
 
-You can build your first app on a small, single database at low cost in the serverless compute tier or a small compute size in the provisioned compute tier. You change the [compute or service tier](scale-single-database.md) manually or programmatically at any time to meet the needs of your solution. You can adjust performance without downtime to your app or to your customers. Dynamic scalability enables your database to transparently respond to rapidly changing resource requirements and enables you to only pay for the resources that you need when you need them.
+You can build your first app on a small, single database at low cost in the serverless compute tier or a small compute size in the provisioned compute tier. You change the [compute or service tier](single-database-scale.md) manually or programmatically at any time to meet the needs of your solution. You can adjust performance without downtime to your app or to your customers. Dynamic scalability enables your database to transparently respond to rapidly changing resource requirements and enables you to only pay for the resources that you need when you need them.
 
 ## Single databases and elastic pools