Merge pull request #115073 from MashaMSFT/move3

Move3

Author: tfosmark

.openpublishing.redirection.json

@@ -52186,6 +52186,66 @@
             "source_path": "articles/sql-database/scripts/sql-database-sync-update-schema.md",
             "redirect_url": "/azure/azure-sql/database/scripts/update-sync-schema-in-sync-group",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-active-geo-replication-portal.md",
+            "redirect_url": "/azure/azure-sql/database/active-geo-replication-configure-portal",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-active-geo-replication.md",
+            "redirect_url": "/azure/azure-sql/database/active-geo-replication-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-advisor-portal.md",
+            "redirect_url": "/azure/azure-sql/database/database-advisor-find-recommendations-portal",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-advisor.md",
+            "redirect_url": "/azure/azure-sql/database/database-advisor-implement-performance-recommendations",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-automatic-tuning-email-notifications.md",
+            "redirect_url": "/azure/azure-sql/database/automatic-tuning-email-notifications-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-automatic-tuning-enable.md",
+            "redirect_url": "/azure/azure-sql/database/automatic-tuning-enable",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-best-practices-data-sync.md",
+            "redirect_url": "/azure/azure-sql/database/sql-data-sync-best-practices",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-connect-query-portal.md",
+            "redirect_url": "/azure/azure-sql/database/connect-query-portal",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-connect-query-r.md",
+            "redirect_url": "/azure/azure-sql/database/connect-query-r",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-connect-query-ssms.md",
+            "redirect_url": "/azure/azure-sql/database/connect-query-ssms",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-connectivity-architecture.md",
+            "redirect_url": "/azure/azure-sql/database/connectivity-architecture",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-copy.md",
+            "redirect_url": "/azure/azure-sql/database/database-copy",
+            "redirect_document_id": true
         }
     ]
 }

articles/sql-database/sql-database-active-geo-replication-portal.md renamed to articles/azure-sql/database/active-geo-replication-configure-portal.md

@@ -14,9 +14,9 @@ ms.date: 02/13/2019
 ---
 # Tutorial: Configure active geo-replication & failover in portal (Azure SQL Database)
 
-This article shows you how to configure [active geo-replication for Azure SQL Database](sql-database-active-geo-replication.md#active-geo-replication-terminology-and-capabilities) using the [Azure portal](https://portal.azure.com) and to initiate failover.
+This article shows you how to configure [active geo-replication for Azure SQL Database](active-geo-replication-overview.md#active-geo-replication-terminology-and-capabilities) using the [Azure portal](https://portal.azure.com) and to initiate failover.
 
-For best practices using auto-failover groups, see [Best practices for Azure SQL Database](sql-database-auto-failover-group.md#best-practices-for-sql-database) and [Best practices for Azure SQL Managed Instance](sql-database-auto-failover-group.md#best-practices-for-sql-managed-instance). 
+For best practices using auto-failover groups, see [Best practices for Azure SQL Database](../../sql-database/sql-database-auto-failover-group.md#best-practices-for-sql-database) and [Best practices for Azure SQL Managed Instance](../../sql-database/sql-database-auto-failover-group.md#best-practices-for-sql-managed-instance). 
 
 
 
@@ -35,27 +35,27 @@ The following steps create a new secondary database in a geo-replication partner
 
 To add a secondary database, you must be the subscription owner or co-owner.
 
-The secondary database has the same name as the primary database and has, by default, the same service tier and compute size. The secondary database can be a single database or a pooled database. For more information, see [DTU-based purchasing model](sql-database-service-tiers-dtu.md) and [vCore-based purchasing model](sql-database-service-tiers-vcore.md).
+The secondary database has the same name as the primary database and has, by default, the same service tier and compute size. The secondary database can be a single database or a pooled database. For more information, see [DTU-based purchasing model](../../sql-database/sql-database-service-tiers-dtu.md) and [vCore-based purchasing model](../../sql-database/sql-database-service-tiers-vcore.md).
 After the secondary is created and seeded, data begins replicating from the primary database to the new secondary database.
 
 > [!NOTE]
 > If the partner database already exists (for example, as a result of terminating a previous geo-replication relationship) the command fails.
 
 1. In the [Azure portal](https://portal.azure.com), browse to the database that you want to set up for geo-replication.
-2. On the SQL Database page, select **geo-replication**, and then select the region to create the secondary database. You can select any region other than the region hosting the primary database, but we recommend the [paired region](../best-practices-availability-paired-regions.md).
+2. On the SQL Database page, select **geo-replication**, and then select the region to create the secondary database. You can select any region other than the region hosting the primary database, but we recommend the [paired region](../../best-practices-availability-paired-regions.md).
 
-    ![Configure geo-replication](./media/sql-database-geo-replication-portal/configure-geo-replication.png)
+    ![Configure geo-replication](./media/active-geo-replication-configure-portal/configure-geo-replication.png)
 3. Select or configure the server and pricing tier for the secondary database.
 
-    ![Configure secondary](./media/sql-database-geo-replication-portal/create-secondary.png)
+    ![Configure secondary](./media/active-geo-replication-configure-portal/create-secondary.png)
 4. Optionally, you can add a secondary database to an elastic pool. To create the secondary database in a pool, click **elastic pool** and select a pool on the target server. A pool must already exist on the target server. This workflow does not create a pool.
 5. Click **Create** to add the secondary.
 6. The secondary database is created and the seeding process begins.
 
-    ![Configure secondary](./media/sql-database-geo-replication-portal/seeding0.png)
+    ![Configure secondary](./media/active-geo-replication-configure-portal/seeding0.png)
 7. When the seeding process is complete, the secondary database displays its status.
 
-    ![Seeding complete](./media/sql-database-geo-replication-portal/seeding-complete.png)
+    ![Seeding complete](./media/active-geo-replication-configure-portal/seeding-complete.png)
 
 ## Initiate a failover
 
@@ -65,7 +65,7 @@ The secondary database can be switched to become the primary.
 2. On the SQL Database blade, select **All settings** > **geo-replication**.
 3. In the **SECONDARIES** list, select the database you want to become the new primary and click **Forced Failover**.
 
-    ![failover](./media/sql-database-geo-replication-failover-portal/secondaries.png)
+    ![failover](./media/active-geo-replication-configure-portal/secondaries.png)
 4. Click **Yes** to begin the failover.
 
 The command immediately switches the secondary database into the primary role. This process normally should complete within 30 sec or less.
@@ -84,11 +84,11 @@ This operation permanently terminates the replication to the secondary database,
 3. In the **SECONDARIES** list, select the database you want to remove from the geo-replication partnership.
 4. Click **Stop Replication**.
 
-    ![Remove secondary](./media/sql-database-geo-replication-portal/remove-secondary.png)
+    ![Remove secondary](./media/active-geo-replication-configure-portal/remove-secondary.png)
 5. A confirmation window opens. Click **Yes** to remove the database from the geo-replication partnership. (Set it to a read-write database not part of any replication.)
 
 ## Next steps
 
-* To learn more about active geo-replication, see [active geo-replication](sql-database-active-geo-replication.md).
-* To learn about auto-failover groups, see [Auto-failover groups](sql-database-auto-failover-group.md)
-* For a business continuity overview and scenarios, see [Business continuity overview](sql-database-business-continuity.md).
+* To learn more about active geo-replication, see [active geo-replication](active-geo-replication-overview.md).
+* To learn about auto-failover groups, see [Auto-failover groups](../../sql-database/sql-database-auto-failover-group.md)
+* For a business continuity overview and scenarios, see [Business continuity overview](../../sql-database/sql-database-business-continuity.md).