Merge pull request #115147 from MashaMSFT/move5

Move5

Author: rmca14

.openpublishing.redirection.json

@@ -52321,6 +52321,66 @@
             "source_path": "articles/sql-database/sql-database-elastic-pool.md",
             "redirect_url": "/azure/azure-sql/database/elastic-pool-overview",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-pool-resource-management.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-pool-resource-management",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-pool-scale.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-pool-scale",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-query-getting-started-vertical.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-query-getting-started-vertical",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-query-getting-started.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-query-getting-started",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-query-horizontal-partitioning.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-query-horizontal-partitioning",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-query-overview.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-query-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-query-vertical-partitioning.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-query-vertical-partitioning",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-add-a-shard.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-add-a-shard",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-configure-deploy-split-and-merge.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-configure-deploy-split-and-merge",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-data-dependent-routing.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-data-dependent-routing",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-faq.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-faq",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-get-started.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-get-started",
+            "redirect_document_id": true
         }
     ]
 }

articles/azure-sql/database/elastic-convert-to-use-elastic-tools.md

@@ -146,15 +146,15 @@ Get-Mappings -ShardMap $ShardMap
 
 ## Summary
 
-Once you have completed the setup, you can begin to use the Elastic Database client library. You can also use [data-dependent routing](../../sql-database/sql-database-elastic-scale-data-dependent-routing.md) and [multi-shard query](../../sql-database/sql-database-elastic-scale-multishard-querying.md).
+Once you have completed the setup, you can begin to use the Elastic Database client library. You can also use [data-dependent routing](elastic-scale-data-dependent-routing.md) and [multi-shard query](../../sql-database/sql-database-elastic-scale-multishard-querying.md).
 
 ## Next steps
 
 Get the PowerShell scripts from [Azure SQL Database-Elastic Database tools scripts](https://gallery.technet.microsoft.com/scriptcenter/Azure-SQL-DB-Elastic-731883db).
 
 The tools are also on GitHub: [Azure/elastic-db-tools](https://github.com/Azure/elastic-db-tools).
 
-Use the split-merge tool to move data to or from a multi-tenant model to a single tenant model. See [Split merge tool](../../sql-database/sql-database-elastic-scale-get-started.md).
+Use the split-merge tool to move data to or from a multi-tenant model to a single tenant model. See [Split merge tool](elastic-scale-get-started.md).
 
 ## Additional resources
 

articles/azure-sql/database/elastic-database-client-library.md

@@ -23,30 +23,30 @@ To download:
 
 ## Documentation
 
-1. [Get started with Elastic Database tools](../../sql-database/sql-database-elastic-scale-get-started.md)
+1. [Get started with Elastic Database tools](elastic-scale-get-started.md)
 2. [Elastic Database features](../../sql-database/sql-database-elastic-scale-introduction.md)
 3. [Shard map management](../../sql-database/sql-database-elastic-scale-shard-map-management.md)
 4. [Migrate existing databases to scale out](elastic-convert-to-use-elastic-tools.md)
-5. [Data dependent routing](../../sql-database/sql-database-elastic-scale-data-dependent-routing.md)
+5. [Data dependent routing](elastic-scale-data-dependent-routing.md)
 6. [Multi-shard queries](../../sql-database/sql-database-elastic-scale-multishard-querying.md)
-7. [Adding a shard using Elastic Database tools](../../sql-database/sql-database-elastic-scale-add-a-shard.md)
+7. [Adding a shard using Elastic Database tools](elastic-scale-add-a-shard.md)
 8. [Multi-tenant applications with elastic database tools and row-level security](../../sql-database/saas-tenancy-elastic-tools-multi-tenant-row-level-security.md)
 9. [Upgrade client library apps](../../sql-database/sql-database-elastic-scale-upgrade-client-library.md) 
-10. [Elastic queries overview](../../sql-database/sql-database-elastic-query-overview.md)
+10. [Elastic queries overview](elastic-query-overview.md)
 11. [Elastic database tools glossary](../../sql-database/sql-database-elastic-scale-glossary.md)
 12. [Elastic Database client library with Entity Framework](../../sql-database/sql-database-elastic-scale-use-entity-framework-applications-visual-studio.md)
 13. [Elastic database client library with Dapper](../../sql-database/sql-database-elastic-scale-working-with-dapper.md)
 14. [Split-merge tool](../../sql-database/sql-database-elastic-scale-overview-split-and-merge.md)
 15. [Performance counters for shard map manager](elastic-database-client-library.md) 
-16. [FAQ for Elastic database tools](../../sql-database/sql-database-elastic-scale-faq.md)
+16. [FAQ for Elastic database tools](elastic-scale-faq.md)
 
 ## Client capabilities
 
 Scaling out applications using *sharding* presents challenges for both the developer as well as the administrator. The client library simplifies the management tasks by providing tools that let both developers and administrators manage scaled-out databases. In a typical example, there are many databases, known as "shards," to manage. Customers are co-located in the same database, and there is one database per customer (a single-tenant scheme). The client library includes these features:
 
 - **Shard Map Management**: A special database called the "shard map manager" is created. Shard map management is the ability for an application to manage metadata about its shards. Developers can use this functionality to register databases as shards, describe mappings of individual sharding keys or key ranges to those databases, and maintain this metadata as the number and composition of databases evolves to reflect capacity changes. Without the elastic database client library, you would need to spend a lot of time writing the management code when implementing sharding. For details, see [Shard map management](../../sql-database/sql-database-elastic-scale-shard-map-management.md).
 
-- **Data dependent routing**: Imagine a request coming into the application. Based on the sharding key value of the request, the application needs to determine the correct database based on the key value. It then opens a connection to the database to process the request. Data dependent routing provides the ability to open connections with a single easy call into the shard map of the application. Data dependent routing was another area of infrastructure code that is now covered by functionality in the elastic database client library. For details, see [Data dependent routing](../../sql-database/sql-database-elastic-scale-data-dependent-routing.md).
+- **Data dependent routing**: Imagine a request coming into the application. Based on the sharding key value of the request, the application needs to determine the correct database based on the key value. It then opens a connection to the database to process the request. Data dependent routing provides the ability to open connections with a single easy call into the shard map of the application. Data dependent routing was another area of infrastructure code that is now covered by functionality in the elastic database client library. For details, see [Data dependent routing](elastic-scale-data-dependent-routing.md).
 - **Multi-shard queries (MSQ)**: Multi-shard querying works when a request involves several (or all) shards. A multi-shard query executes the same T-SQL code on all shards or a set of shards. The results from the participating shards are merged into an overall result set using UNION ALL semantics. The functionality as exposed through the client library handles many tasks, including: connection management, thread management, fault handling, and intermediate results processing. MSQ can query up to hundreds of shards. For details, see [Multi-shard querying](../../sql-database/sql-database-elastic-scale-multishard-querying.md).
 
 In general, customers using elastic database tools can expect to get full T-SQL functionality when submitting shard-local operations as opposed to cross-shard operations that have their own semantics.
@@ -57,10 +57,10 @@ In general, customers using elastic database tools can expect to get full T-SQL
 
 - Elastic Database Client Library ([Java](https://search.maven.org/#search%7Cga%7C1%7Ca%3A%22azure-elasticdb-tools%22), [.NET](https://www.nuget.org/packages/Microsoft.Azure.SqlDatabase.ElasticScale.Client/)) - to **download** the library.
 
-- [Get started with elastic database tools](../../sql-database/sql-database-elastic-scale-get-started.md) - to try the **sample app** that demonstrates client functions.
+- [Get started with elastic database tools](elastic-scale-get-started.md) - to try the **sample app** that demonstrates client functions.
 
 - GitHub ([Java](https://github.com/Microsoft/elastic-db-tools-for-java/blob/master/README.md), [.NET](https://github.com/Azure/elastic-db-tools)) - to make contributions to the code.
-- [Azure SQL Database elastic query overview](../../sql-database/sql-database-elastic-query-overview.md) - to use elastic queries.
+- [Azure SQL Database elastic query overview](elastic-query-overview.md) - to use elastic queries.
 
 - [Moving data between scaled-out cloud databases](../../sql-database/sql-database-elastic-scale-overview-split-and-merge.md) - for instructions on using the **split-merge tool**.
 

articles/azure-sql/database/elastic-database-perf-counters.md

@@ -14,9 +14,9 @@ ms.date: 02/07/2019
 ---
 # Create performance counters to track performance of shard map manager
 
-Performance counters are used to track the performance of [data dependent routing](../../sql-database/sql-database-elastic-scale-data-dependent-routing.md) operations. These counters are accessible in the Performance Monitor, under the "Elastic Database: Shard Management" category.
+Performance counters are used to track the performance of [data dependent routing](elastic-scale-data-dependent-routing.md) operations. These counters are accessible in the Performance Monitor, under the "Elastic Database: Shard Management" category.
 
-You can capture the performance of a [shard map manager](../../sql-database/sql-database-elastic-scale-shard-map-management.md), especially when using [data dependent routing](../../sql-database/sql-database-elastic-scale-data-dependent-routing.md). Counters are created with methods of the Microsoft.Azure.SqlDatabase.ElasticScale.Client class.  
+You can capture the performance of a [shard map manager](../../sql-database/sql-database-elastic-scale-shard-map-management.md), especially when using [data dependent routing](elastic-scale-data-dependent-routing.md). Counters are created with methods of the Microsoft.Azure.SqlDatabase.ElasticScale.Client class.  
 
 
 **For the latest version:** Go to [Microsoft.Azure.SqlDatabase.ElasticScale.Client](https://www.nuget.org/packages/Microsoft.Azure.SqlDatabase.ElasticScale.Client/). See also [Upgrade an app to use the latest elastic database client library](../../sql-database/sql-database-elastic-scale-upgrade-client-library.md).

articles/azure-sql/database/elastic-database-recovery-manager.md

@@ -37,7 +37,7 @@ The GSM and LSM may become out of sync for the following reasons:
 For more information about Azure SQL Database Elastic Database tools, geo-replication and Restore, see the following:
 
 * [Overview: Cloud business continuity and database disaster recovery with SQL Database](../../sql-database/sql-database-business-continuity.md)
-* [Get started with elastic database tools](../../sql-database/sql-database-elastic-scale-get-started.md)  
+* [Get started with elastic database tools](elastic-scale-get-started.md)  
 * [ShardMap Management](../../sql-database/sql-database-elastic-scale-shard-map-management.md)
 
 ## Retrieving RecoveryManager from a ShardMapManager

articles/azure-sql/database/elastic-pool-overview.md

@@ -124,7 +124,7 @@ The following steps can help you estimate whether a pool is more cost-effective
 5. Compare the pool price from Step 5 to the price of using the appropriate compute sizes for single databases.
 
 > [!IMPORTANT]
-> If the number of databases in a pool approaches the maximum supported, make sure to consider [Resource management in dense elastic pools](../../sql-database/sql-database-elastic-pool-resource-management.md).
+> If the number of databases in a pool approaches the maximum supported, make sure to consider [Resource management in dense elastic pools](elastic-pool-resource-management.md).
 
 ## Using other SQL Database features with elastic pools
 
@@ -221,7 +221,7 @@ For more information, see [create SQL Database alerts in Azure portal](../../sql
 ## Next steps
 
 - For pricing information, see [Elastic pool pricing](https://azure.microsoft.com/pricing/details/sql-database/elastic).
-- To scale elastic pools, see [Scaling elastic pools](../../sql-database/sql-database-elastic-pool-scale.md) and [Scale an elastic pool - sample code](scripts/monitor-and-scale-pool-powershell.md)
+- To scale elastic pools, see [Scaling elastic pools](elastic-pool-scale.md) and [Scale an elastic pool - sample code](scripts/monitor-and-scale-pool-powershell.md)
 - To learn more about design patterns for SaaS applications using elastic pools, see [Design Patterns for Multi-tenant SaaS Applications with Azure SQL Database](../../sql-database/saas-tenancy-app-design-patterns.md).
 - For a SaaS tutorial using elastic pools, see [Introduction to the Wingtip SaaS application](../../sql-database/saas-dbpertenant-wingtip-app-overview.md).
-- To learn about resource management in elastic pools with many databases, see [Resource management in dense elastic pools](../../sql-database/sql-database-elastic-pool-resource-management.md).
+- To learn about resource management in elastic pools with many databases, see [Resource management in dense elastic pools](elastic-pool-resource-management.md).

articles/sql-database/sql-database-elastic-pool-resource-management.md renamed to articles/azure-sql/database/elastic-pool-resource-management.md

@@ -28,7 +28,7 @@ The primary design goal of elastic pools is to be cost-effective. For this reaso
 This approach allows customers to use dense elastic pools to achieve adequate performance and major cost savings. However, if the workload against many databases in a dense pool is sufficiently intense, resource contention becomes significant. Resource contention reduces user workload performance, and can negatively impact internal processes.
 
 > [!IMPORTANT]
-> In dense pools with many active databases, it may not be feasible to increase the number of databases in the pool up to the maximums documented for [DTU](../azure-sql/database/resource-limits-dtu-elastic-pools.md) and [vCore](sql-database-vcore-resource-limits-elastic-pools.md) elastic pools.
+> In dense pools with many active databases, it may not be feasible to increase the number of databases in the pool up to the maximums documented for [DTU](resource-limits-dtu-elastic-pools.md) and [vCore](../../sql-database/sql-database-vcore-resource-limits-elastic-pools.md) elastic pools.
 >
 > The number of databases that can be placed in dense pools without causing resource contention and performance problems depends on the number of concurrently active databases, and on resource consumption by user workloads in each database. This number can change over time as user workloads change.