Merge pull request #115158 from MashaMSFT/move6

Move6

Author: rmca14

.openpublishing.redirection.json

@@ -52381,6 +52381,71 @@
             "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
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-glossary.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-glossary",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-manage-credentials.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-manage-credentials",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-introduction.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-introduction",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-multishard-querying.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-multishard-querying",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-overview-split-and-merge.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-overview-split-and-merge",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-shard-map-management.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-shard-map-management",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-split-merge-security-configuration.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-split-merge-security-configuration",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-upgrade-client-library.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-upgrade-client-library",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-use-entity-framework-applications-visual-studio.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-use-entity-framework-applications-visual-studio",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-scale-working-with-dapper.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-scale-working-with-dapper",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-elastic-transactions-overview.md",
+            "redirect_url": "/azure/azure-sql/database/elastic-transactions-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-export.md",
+            "redirect_url": "/azure/azure-sql/database/database-export",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-file-space-management.md",
+            "redirect_url": "/azure/azure-sql/database/file-space-manage",
+            "redirect_document_id": true
         }
     ]
 }

articles/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac.md

@@ -40,7 +40,7 @@ To complete this article, you need:
 
 ## Prepare a BACPAC file
 
-A BACPAC file is shared in [GitHub](https://github.com/Azure/azure-docs-json-samples/raw/master/tutorial-sql-extension/SQLDatabaseExtension.bacpac). To create your own, see [Export an Azure SQL database to a BACPAC file](../../sql-database/sql-database-export.md). If you choose to publish the file to your own location, you must update the template later in the tutorial.
+A BACPAC file is shared in [GitHub](https://github.com/Azure/azure-docs-json-samples/raw/master/tutorial-sql-extension/SQLDatabaseExtension.bacpac). To create your own, see [Export an Azure SQL database to a BACPAC file](../../azure-sql/database/database-export.md). If you choose to publish the file to your own location, you must update the template later in the tutorial.
 
 The BACPAC file must be stored in an Azure Storage account before it can be imported by using an ARM template. The following PowerShell script prepares the BACPAC file with these steps:
 

articles/azure-sql/database/database-copy.md

@@ -189,4 +189,4 @@ The following errors can be encountered while copying a database in Azure SQL Da
 ## Next steps
 
 * For information about logins, see [Manage logins](../../sql-database/sql-database-manage-logins.md) and [How to manage Azure SQL Database security after disaster recovery](../../sql-database/sql-database-geo-replication-security-config.md).
-* To export a database, see [Export the database to a BACPAC](../../sql-database/sql-database-export.md).
+* To export a database, see [Export the database to a BACPAC](database-export.md).

articles/sql-database/sql-database-export.md renamed to articles/azure-sql/database/database-export.md

@@ -18,7 +18,7 @@ When you need to export a database for archiving or for moving to another platfo
 
 ## Considerations
 
-- For an export to be transactionally consistent, you must ensure either that no write activity is occurring during the export, or that you are exporting from a [transactionally consistent copy](../azure-sql/database/database-copy.md) of your database.
+- For an export to be transactionally consistent, you must ensure either that no write activity is occurring during the export, or that you are exporting from a [transactionally consistent copy](database-copy.md) of your database.
 - If you are exporting to blob storage, the maximum size of a BACPAC file is 200 GB. To archive a larger BACPAC file, export to local storage.
 - Exporting a BACPAC file to Azure premium storage using the methods discussed in this article is not supported.
 - Storage behind a firewall is currently not supported.
@@ -29,28 +29,28 @@ When you need to export a database for archiving or for moving to another platfo
   - Use a [clustered index](https://msdn.microsoft.com/library/ms190457.aspx) with non-null values on all large tables. Without clustered indexes, an export may fail if it takes longer than 6-12 hours. This is because the export service needs to complete a table scan to try to export entire table. A good way to determine if your tables are optimized for export is to run **DBCC SHOW_STATISTICS** and make sure that the *RANGE_HI_KEY* is not null and its value has good distribution. For details, see [DBCC SHOW_STATISTICS](https://msdn.microsoft.com/library/ms174384.aspx).
 
 > [!NOTE]
-> BACPACs are not intended to be used for backup and restore operations. Azure automatically creates backups for every user database. For details, see [business continuity overview](sql-database-business-continuity.md) and [SQL Database backups](sql-database-automated-backups.md).
+> BACPACs are not intended to be used for backup and restore operations. Azure automatically creates backups for every user database. For details, see [business continuity overview](../../sql-database/sql-database-business-continuity.md) and [SQL Database backups](../../sql-database/sql-database-automated-backups.md).
 
 ## Azure portal
 
-Exporting a BACPAC of a database from an [Azure SQL Managed Instance](sql-database-managed-instance.md) using the Azure Portal is not currently supported. Use SQL Server Management Studio or SQLPackage instead.
+Exporting a BACPAC of a database from an [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md) using the Azure Portal is not currently supported. Use SQL Server Management Studio or SQLPackage instead.
 
 > [!NOTE]
 > Machines processing import/export requests submitted through the Azure portal or PowerShell need to store the BACPAC file as well as temporary files generated by the Data-Tier Application Framework (DacFX). The disk space required varies significantly among databases with the same size and can require disk space up to 3 times the size of the database. Machines running the import/export request only have  450GB local disk space. As a result, some requests may fail with the error `There is not enough space on the disk`. In this case, the workaround is to run sqlpackage.exe on a machine with enough local disk space. We encourage using [SqlPackage](#sqlpackage-utility) to import/export databases larger than 150GB to avoid this issue.
 
 1. To export a database using the [Azure portal](https://portal.azure.com), open the page for your database and click **Export** on the toolbar.
 
-   ![Database export](./media/sql-database-export/database-export1.png)
+   ![Database export](./media/database-export/database-export1.png)
 
 2. Specify the BACPAC filename, select an existing Azure storage account and container for the export, and then provide the appropriate credentials for access to the source database. A SQL **Server admin login** is needed here even if you are the Azure admin, as being an Azure admin does not equate to having admin permissions in Azure SQL Database or Azure SQL Managed Instance.
 
-    ![Database export](./media/sql-database-export/database-export2.png)
+    ![Database export](./media/database-export/database-export2.png)
 
 3. Click **OK**.
 
 4. To monitor the progress of the export operation, open the page for the server containing the database being exported. Under to **Settings** and then click **Import/Export history**.
 
-   ![export history](./media/sql-database-export/export-history.png)
+   ![export history](./media/database-export/export-history.png)
 
 ## SQLPackage utility
 
@@ -71,7 +71,7 @@ The newest versions of SQL Server Management Studio provide a wizard to export a
 ## PowerShell
 
 > [!NOTE]
-> [Azure SQL Managed Instance](sql-database-managed-instance.md) does not currently support exporting a database to a BACPAC file using Azure PowerShell. To export a managed instance into a BACPAC file, use SQL Server Management Studio or SQLPackage.
+> [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md) does not currently support exporting a database to a BACPAC file using Azure PowerShell. To export a managed instance into a BACPAC file, use SQL Server Management Studio or SQLPackage.
 
 Use the [New-AzSqlDatabaseExport](/powershell/module/az.sql/new-azsqldatabaseexport) cmdlet to submit an export database request to the Azure SQL Database service. Depending on the size of your database, the export operation may take some time to complete.
 
@@ -98,10 +98,10 @@ $exportStatus
 
 ## Next steps
 
-- To learn about long-term backup retention of a single databases and pooled databases as an alternative to exported a database for archive purposes, see [Long-term backup retention](sql-database-long-term-retention.md). You can use SQL Agent jobs to schedule [copy-only database backups](https://docs.microsoft.com/sql/relational-databases/backup-restore/copy-only-backups-sql-server) as an alternative to long-term backup retention.
+- To learn about long-term backup retention of a single databases and pooled databases as an alternative to exported a database for archive purposes, see [Long-term backup retention](../../sql-database/sql-database-long-term-retention.md). You can use SQL Agent jobs to schedule [copy-only database backups](https://docs.microsoft.com/sql/relational-databases/backup-restore/copy-only-backups-sql-server) as an alternative to long-term backup retention.
 - For a SQL Server Customer Advisory Team blog about migrating using BACPAC files, see [Migrating from SQL Server to Azure SQL Database using BACPAC Files](https://blogs.msdn.microsoft.com/sqlcat/2016/10/20/migrating-from-sql-server-to-azure-sql-database-using-bacpac-files/).
 - To learn about importing a BACPAC to a SQL Server database, see [Import a BACPAC to a SQL Server database](https://msdn.microsoft.com/library/hh710052.aspx).
 - To learn about exporting a BACPAC from a SQL Server database, see [Export a Data-tier Application](https://docs.microsoft.com/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
-- To learn about using the Data Migration Service to migrate a database, see [Migrate SQL Server to Azure SQL Database offline using DMS](../dms/tutorial-sql-server-to-azure-sql.md).
-- If you are exporting from SQL Server as a prelude to migration to Azure SQL Database, see [Migrate a SQL Server database to Azure SQL Database](sql-database-single-database-migrate.md).
+- To learn about using the Data Migration Service to migrate a database, see [Migrate SQL Server to Azure SQL Database offline using DMS](../../dms/tutorial-sql-server-to-azure-sql.md).
+- If you are exporting from SQL Server as a prelude to migration to Azure SQL Database, see [Migrate a SQL Server database to Azure SQL Database](../../sql-database/sql-database-single-database-migrate.md).
 - To learn how to manage and share storage keys and shared access signatures securely, see [Azure Storage Security Guide](https://docs.microsoft.com/azure/storage/common/storage-security-guide).

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

@@ -15,20 +15,20 @@ ms.date: 01/25/2019
 ---
 # Migrate existing databases to scale out
 
-Easily manage your existing scaled-out sharded databases using tools (such as the [Elastic Database client library](elastic-database-client-library.md)). First convert an existing set of databases to use the [shard map manager](../../sql-database/sql-database-elastic-scale-shard-map-management.md).
+Easily manage your existing scaled-out sharded databases using tools (such as the [Elastic Database client library](elastic-database-client-library.md)). First convert an existing set of databases to use the [shard map manager](elastic-scale-shard-map-management.md).
 
 ## Overview
 
 To migrate an existing sharded database:
 
-1. Prepare the [shard map manager database](../../sql-database/sql-database-elastic-scale-shard-map-management.md).
+1. Prepare the [shard map manager database](elastic-scale-shard-map-management.md).
 2. Create the shard map.
 3. Prepare the individual shards.  
 4. Add mappings to the shard map.
 
 These techniques can be implemented using either the [.NET Framework client library](https://www.nuget.org/packages/Microsoft.Azure.SqlDatabase.ElasticScale.Client/), or the PowerShell scripts found at [Azure SQL Database - Elastic Database tools scripts](https://gallery.technet.microsoft.com/scriptcenter/Azure-SQL-DB-Elastic-731883db). The examples here use the PowerShell scripts.
 
-For more information about the ShardMapManager, see [Shard map management](../../sql-database/sql-database-elastic-scale-shard-map-management.md). For an overview of the elastic database tools, see [Elastic Database features overview](../../sql-database/sql-database-elastic-scale-introduction.md).
+For more information about the ShardMapManager, see [Shard map management](elastic-scale-shard-map-management.md). For an overview of the elastic database tools, see [Elastic Database features overview](elastic-scale-introduction.md).
 
 ## Prepare the shard map manager database
 
@@ -57,7 +57,7 @@ $ShardMapManager = Get-ShardMapManager -UserName '<user_name>' -Password '<passw
 
 Select the type of shard map to create. The choice depends on the database architecture:
 
-1. Single tenant per database (For terms, see the [glossary](../../sql-database/sql-database-elastic-scale-glossary.md).)
+1. Single tenant per database (For terms, see the [glossary](elastic-scale-glossary.md).)
 2. Multiple tenants per database (two types):
    1. List mapping
    2. Range mapping
@@ -146,7 +146,7 @@ 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](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](elastic-scale-multishard-querying.md).
 
 ## Next steps