Merge pull request #115199 from MashaMSFT/move9

Move9

Author: tfosmark

.openpublishing.redirection.json

@@ -4216,7 +4216,7 @@
         },
         {
             "source_path": "articles/sql-database/sql-database-single-database-resources.md",
-            "redirect_url": "/azure/sql-database/sql-database-single-database-scale",
+            "redirect_url": "/azure/sql-database/single-database-scale",
             "redirect_document_id": false
         },
         {
@@ -18244,7 +18244,7 @@
             "redirect_document_id": false
         },
         {
-            "source_path": "articles/sql-database/sql-database-get-started-portal.md",
+            "source_path": "articles/sql-database/quickstart-create-single-database.md",
             "redirect_url": "/azure/sql-database/sql-database-single-database-get-started",
             "redirect_document_id": false
         },
@@ -18405,12 +18405,12 @@
         },
         {
             "source_path": "articles/sql-database/sql-database-scale-up-powershell.md",
-            "redirect_url": "/azure/sql-database/sql-database-single-database-scale",
+            "redirect_url": "/azure/sql-database/single-database-scale",
             "redirect_document_id": false
         },
         {
             "source_path": "articles/sql-database/sql-database-scale-up.md",
-            "redirect_url": "/azure/sql-database/sql-database-single-database-scale",
+            "redirect_url": "/azure/sql-database/single-database-scale",
             "redirect_document_id": false
         },
         {
@@ -52586,6 +52586,146 @@
             "source_path": "articles/sql-database/sql-database-single-database.md",
             "redirect_url": "/azure/azure-sql/database/single-database-overview",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-geo-replication-security-config.md",
+            "redirect_url": "/azure/azure-sql/database/geo-replication-security-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-json-features.md",
+            "redirect_url": "/azure/azure-sql/database/json-features",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-database-failover-group-tutorial.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-add-single-database-failover-group",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-database-get-started-template.md",
+            "redirect_url": "/azure/azure-sql/database/quickstart-single-database-arm-template",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-database-get-started.md",
+            "redirect_url": "/azure/azure-sql/database/quickstart-create-single-database",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-database-migrate.md",
+            "redirect_url": "/azure/azure-sql/database/migrate-to-database-from-sql-server",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-database-quickstart-guide.md",
+            "redirect_url": "/azure/azure-sql/database/quickstart-content-reference-guide",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-database-scale.md",
+            "redirect_url": "/azure/azure-sql/database/single-database-scale",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-single-databases-manage.md",
+            "redirect_url": "/azure/azure-sql/database/single-database-manage",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-stream-analytics.md",
+            "redirect_url": "/azure/azure-sql/database/stream-data-stream-analytics-integration",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-sync-data.md",
+            "redirect_url": "/azure/azure-sql/database/sql-data-sync-data-sql-server-sql-database",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-sync-monitor-oms.md",
+            "redirect_url": "/azure/azure-sql/database/sql-data-sync-monitor-sync",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-transact-sql-information.md",
+            "redirect_url": "/azure/azure-sql/database/transact-sql-tsql-differences-sql-server",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-troubleshoot-data-sync.md",
+            "redirect_url": "/azure/azure-sql/database/sql-data-sync-troubleshoot",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-tutorial-clustering-model-build.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-clustering-model-build",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-tutorial-clustering-model-deploy.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-clustering-model-deploy",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-tutorial-clustering-model-prepare-data.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-clustering-model-prepare-data",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-tutorial-predictive-model-build-compare.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-predictive-model-build-compare",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-tutorial-predictive-model-deploy.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-predictive-model-deploy",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-tutorial-predictive-model-prepare-data.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-predictive-model-prepare-data",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-update-sync-schema.md",
+            "redirect_url": "/azure/azure-sql/database/sql-data-sync-update-sync-schema",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-vcore-resource-limits-elastic-pools.md",
+            "redirect_url": "/azure/azure-sql/database/resource-limits-vcore-elastic-pools",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-vcore-resource-limits-single-databases.md",
+            "redirect_url": "/azure/azure-sql/database/resource-limits-vcore-single-databases",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-vnet-service-endpoint-rule-overview.md",
+            "redirect_url": "/azure/azure-sql/database/vnet-service-endpoint-rule-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-xevent-code-event-file.md",
+            "redirect_url": "/azure/azure-sql/database/xevent-code-event-file",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-xevent-code-ring-buffer.md",
+            "redirect_url": "/azure/azure-sql/database/xevent-code-ring-buffer",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-xevent-db-diff-from-svr.md",
+            "redirect_url": "/azure/azure-sql/database/xevent-db-diff-from-svr",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/tutorial-sqlite-db-to-azure-sql-serverless-offline.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-sqlite-db-to-azure-sql-serverless-offline",
+            "redirect_document_id": true
         }
     ]
 }

articles/app-service/manage-scale-up.md

@@ -63,7 +63,7 @@ If your app depends on other services, such as Azure SQL Database or Azure Stora
 
     ![Navigate to resource group page to scale up your Azure app](./media/web-sites-scale/ResourceGroup.png)
 
-    To scale up the related resource, see the documentation for the specific resource type. For example, to scale up a single SQL Database, see [Scale single database resources in Azure SQL Database](../sql-database/sql-database-single-database-scale.md). To scale up a Azure Database for MySQL resource, see [Scale MySQL resources](../mysql/concepts-pricing-tiers.md#scale-resources).
+    To scale up the related resource, see the documentation for the specific resource type. For example, to scale up a single SQL Database, see [Scale single database resources in Azure SQL Database](../azure-sql/database/single-database-scale.md). To scale up a Azure Database for MySQL resource, see [Scale MySQL resources](../mysql/concepts-pricing-tiers.md#scale-resources).
 
 <a name="OtherFeatures"></a>
 <a name="devfeatures"></a>

articles/azure-databricks/databricks-extract-load-sql-data-warehouse.md

@@ -364,7 +364,7 @@ As mentioned earlier, the Azure Synapse connector uses Azure Blob storage as tem
    > [!NOTE]
    > This sample uses the `forward_spark_azure_storage_credentials` flag, which causes Azure Synapse to access data from blob storage using an Access Key. This is the only supported method of authentication.
    >
-   > If your Azure Blob Storage is restricted to select virtual networks, Azure Synapse requires [Managed Service Identity instead of Access Keys](../sql-database/sql-database-vnet-service-endpoint-rule-overview.md#impact-of-using-vnet-service-endpoints-with-azure-storage). This will cause the error "This request is not authorized to perform this operation."
+   > If your Azure Blob Storage is restricted to select virtual networks, Azure Synapse requires [Managed Service Identity instead of Access Keys](../azure-sql/database/vnet-service-endpoint-rule-overview.md#impact-of-using-vnet-service-endpoints-with-azure-storage). This will cause the error "This request is not authorized to perform this operation."
 
 6. Connect to the SQL database and verify that you see a database named **SampleTable**.
 

articles/azure-functions/functions-scenario-database-table-cleanup.md

@@ -17,13 +17,13 @@ If this is your first experience working with C# Functions, you should read the
 
 + Complete the steps in the article [Create your first function using Visual Studio](functions-create-your-first-function-visual-studio.md) to create a local function app that targets version 2.x or a later version of the runtime. You must also have published your project to a function app in Azure.
 
-+ This article demonstrates a Transact-SQL command that executes a bulk cleanup operation in the **SalesOrderHeader** table in the AdventureWorksLT sample database. To create the AdventureWorksLT sample database, complete the steps in the article [Create an Azure SQL database in the Azure portal](../sql-database/sql-database-get-started-portal.md).
++ This article demonstrates a Transact-SQL command that executes a bulk cleanup operation in the **SalesOrderHeader** table in the AdventureWorksLT sample database. To create the AdventureWorksLT sample database, complete the steps in the article [Create an Azure SQL database in the Azure portal](../sql-database/quickstart-create-single-database.md).
 
 + You must add a [server-level firewall rule](../sql-database/sql-database-get-started-portal-firewall.md) for the public IP address of the computer you use for this quickstart. This rule is required to be able access the SQL database instance from your local computer.  
 
 ## Get connection information
 
-You need to get the connection string for the database you created when you completed [Create an Azure SQL database in the Azure portal](../sql-database/sql-database-get-started-portal.md).
+You need to get the connection string for the database you created when you completed [Create an Azure SQL database in the Azure portal](../sql-database/quickstart-create-single-database.md).
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -318,7 +318,7 @@ The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise s
 
 ## SQL Database limits
 
-For SQL Database limits, see [SQL Database resource limits for single databases](../../sql-database/sql-database-vcore-resource-limits-single-databases.md), [SQL Database resource limits for elastic pools and pooled databases](../../sql-database/sql-database-vcore-resource-limits-elastic-pools.md), and [SQL Database resource limits for managed instances](../../sql-database/sql-database-managed-instance-resource-limits.md).
+For SQL Database limits, see [SQL Database resource limits for single databases](../../azure-sql/database/resource-limits-vcore-single-databases.md), [SQL Database resource limits for elastic pools and pooled databases](../../azure-sql/database/resource-limits-vcore-elastic-pools.md), and [SQL Database resource limits for managed instances](../../sql-database/sql-database-managed-instance-resource-limits.md).
 
 ## SQL Data Warehouse limits
 

articles/azure-sql/database/active-geo-replication-overview.md

@@ -104,7 +104,7 @@ To achieve real business continuity, adding database redundancy between datacent
 
 ## Preparing secondary database for failover
 
-To ensure that your application can immediately access the new primary after failover,  ensure the authentication requirements for your secondary server and database are properly configured. For details, see [SQL Database security after disaster recovery](../../sql-database/sql-database-geo-replication-security-config.md). To guarantee compliance after failover, make sure that the backup retention policy on the secondary database matches that of the primary. These settings are not part of the database and are not replicated. By default, the secondary will be configured with a default PITR retention period of seven days. For details, see [SQL Database automated backups](../../sql-database/sql-database-automated-backups.md).
+To ensure that your application can immediately access the new primary after failover,  ensure the authentication requirements for your secondary server and database are properly configured. For details, see [SQL Database security after disaster recovery](geo-replication-security-configure.md). To guarantee compliance after failover, make sure that the backup retention policy on the secondary database matches that of the primary. These settings are not part of the database and are not replicated. By default, the secondary will be configured with a default PITR retention period of seven days. For details, see [SQL Database automated backups](../../sql-database/sql-database-automated-backups.md).
 
 > [!IMPORTANT]
 > If your database is a member of a failover group, you cannot initiate its failover using the geo-replication failover command. Use the failover command for the group. If you need to failover an individual database, you must remove it from the failover group first. See  [failover groups](../../sql-database/sql-database-auto-failover-group.md) for details.
@@ -289,4 +289,4 @@ As discussed previously, active geo-replication can also be managed programmatic
 - For a business continuity overview and scenarios, see [Business continuity overview](../../sql-database/sql-database-business-continuity.md)
 - To learn about Azure SQL Database automated backups, see [SQL Database automated backups](../../sql-database/sql-database-automated-backups.md).
 - To learn about using automated backups for recovery, see [Restore a database from the service-initiated backups](../../sql-database/sql-database-recovery-using-backups.md).
-- To learn about authentication requirements for a new primary server and database, see [SQL Database security after disaster recovery](../../sql-database/sql-database-geo-replication-security-config.md).
+- To learn about authentication requirements for a new primary server and database, see [SQL Database security after disaster recovery](geo-replication-security-configure.md).

articles/azure-sql/database/connect-query-portal.md

@@ -24,7 +24,7 @@ In this quickstart, you'll use the query editor to run Transact-SQL (T-SQL) quer
 
 Completing this quickstart requires the AdventureWorksLT sample database. If you don't have a working copy of the AdventureWorksLT SQL Database, the following quickstart quickly creates one:
 
-- [Quickstart: Create an Azure SQL Database using the Azure portal, PowerShell, or Azure CLI](../../sql-database/sql-database-single-database-get-started.md) 
+- [Quickstart: Create an Azure SQL Database using the Azure portal, PowerShell, or Azure CLI](quickstart-create-single-database.md) 
 
 ### Configure network settings
 
@@ -186,4 +186,4 @@ There are a few things to know when working with the query editor.
 
 ## Next steps
 
-To learn more about the Transact-SQL (T-SQL) supported in Azure SQL Database, see [Resolving Transact-SQL differences during migration to SQL Database](../../sql-database/sql-database-transact-sql-information.md).
+To learn more about the Transact-SQL (T-SQL) supported in Azure SQL Database, see [Resolving Transact-SQL differences during migration to SQL Database](transact-sql-tsql-differences-sql-server.md).

articles/azure-sql/database/connect-query-r.md

@@ -25,7 +25,7 @@ In this quickstart, you use R with Machine Learning Services to connect to an Az
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
-- An [Azure SQL Database](../../sql-database/sql-database-single-database-get-started.md)
+- An [Azure SQL Database](quickstart-create-single-database.md)
 - [Machine Learning Services](machine-learning-services-overview.md) with R enabled.
 - [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS)
 

articles/azure-sql/database/connect-query-ssms.md

@@ -23,7 +23,7 @@ In this quickstart, you'll learn how to use SQL Server Management Studio (SSMS)
 Completing this quickstart requires the following items:
 
 - [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms/).
-- The AdventureWorksLT sample database. If you need a working copy of the AdventureWorksLT database, create one by completing the [Create an Azure SQL database](../../sql-database/sql-database-single-database-get-started.md) quickstart.
+- The AdventureWorksLT sample database. If you need a working copy of the AdventureWorksLT database, create one by completing the [Create an Azure SQL database](quickstart-create-single-database.md) quickstart.
     - The scripts in this article are written to use the AdventureWorksLT database. If you are using a SQL Managed Instance, you must either import the AdventureWorks database into an instance database or modify the scripts in this article to use the Wide World Importers database.
 
 If you simply want to run some ad-hoc queries without installing SSMS, see [Quickstart: Use the Azure portal's query editor to query a SQL database](connect-query-portal.md).