Merge pull request #115269 from MashaMSFT/move12

Move12

Author: Jak-MS

.openpublishing.redirection.json

@@ -52981,6 +52981,146 @@
             "source_path": "articles/sql-database/sql-database-managed-instance-transactional-replication.md",
             "redirect_url": "/azure/azure-sql/database/transactional-replication-overview",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-monitor-tune-overview.md",
+            "redirect_url": "/azure/azure-sql/database/monitor-tune-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-move-resources-across-regions.md",
+            "redirect_url": "/azure/azure-sql/database/move-resources-across-regions",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-planned-maintenance.md",
+            "redirect_url": "/azure/azure-sql/database/planned-maintenance",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-powershell-samples.md",
+            "redirect_url": "/azure/azure-sql/database/powershell-script-content-guide",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-purchase-models.md",
+            "redirect_url": "/azure/azure-sql/database/purchasing-models",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-read-scale-out.md",
+            "redirect_url": "/azure/azure-sql/database/read-scale-out",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-recovery-using-backups.md",
+            "redirect_url": "/azure/azure-sql/database/recovery-using-backups",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-release-notes.md",
+            "redirect_url": "/azure/azure-sql/database/doc-changes-updates-release-notes",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-reserved-capacity.md",
+            "redirect_url": "/azure/azure-sql/database/reserved-capacity-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-resource-health.md",
+            "redirect_url": "/azure/azure-sql/database/use-resource-health-troubleshoot-connectivity",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-resource-manager-samples.md",
+            "redirect_url": "/azure/azure-sql/database/arm-templates-content-guide",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-scale-resources.md",
+            "redirect_url": "/azure/azure-sql/database/scale-resources",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-security-best-practice.md",
+            "redirect_url": "/azure/azure-sql/database/security-best-practice",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-security-overview.md",
+            "redirect_url": "/azure/azure-sql/database/security-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-service-tier-business-critical.md",
+            "redirect_url": "/azure/azure-sql/database/service-tier-business-critical",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-service-tier-general-purpose.md",
+            "redirect_url": "/azure/azure-sql/database/service-tier-general-purpose",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-service-tiers-vcore.md",
+            "redirect_url": "/azure/azure-sql/database/service-tiers-vcore",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-spark-connector.md",
+            "redirect_url": "/azure/azure-sql/database/spark-connector",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-technical-overview.md",
+            "redirect_url": "/azure/azure-sql/database/technical-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-threat-detection-overview.md",
+            "redirect_url": "/azure/azure-sql/database/threat-detection-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-threat-detection.md",
+            "redirect_url": "/azure/azure-sql/database/threat-detection",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-vulnerability-assessment.md",
+            "redirect_url": "/azure/azure-sql/database/sql-vulnerability-assessment",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/transparent-data-encryption-azure-sql.md",
+            "redirect_url": "/azure/azure-sql/database/transparent-data-encryption-tde-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/transparent-data-encryption-byok-azure-sql-configure.md",
+            "redirect_url": "/azure/azure-sql/database/transparent-data-encryption-byok-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/transparent-data-encryption-byok-azure-sql-key-rotation.md",
+            "redirect_url": "/azure/azure-sql/database/transparent-data-encryption-byok-key-rotation",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/transparent-data-encryption-byok-azure-sql-remove-tde-protector.md",
+            "redirect_url": "/azure/azure-sql/database/transparent-data-encryption-byok-remove-tde-protector",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/transparent-data-encryption-byok-azure-sql.md",
+            "redirect_url": "/azure/azure-sql/database/transparent-data-encryption-byok-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/troubleshoot-connectivity-issues-microsoft-azure-sql-database.md",
+            "redirect_url": "/azure/azure-sql/database/troubleshoot-common-errors-issues",
+            "redirect_document_id": true
         }
     ]
 }

articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md

@@ -10,7 +10,7 @@ ms.custom: mvc, devcenter, vs-azure, seodec18
 
 # Tutorial: Deploy an ASP.NET app to Azure with Azure SQL Database
 
-[Azure App Service](overview.md) provides a highly scalable, self-patching web hosting service. This tutorial shows you how to deploy a data-driven ASP.NET app in App Service and connect it to [Azure SQL Database](../sql-database/sql-database-technical-overview.md). When you're finished, you have an ASP.NET app running in Azure and connected to SQL Database.
+[Azure App Service](overview.md) provides a highly scalable, self-patching web hosting service. This tutorial shows you how to deploy a data-driven ASP.NET app in App Service and connect it to [Azure SQL Database](../azure-sql/database/technical-overview.md). When you're finished, you have an ASP.NET app running in Azure and connected to SQL Database.
 
 ![Published ASP.NET application in Azure App Service](./media/app-service-web-tutorial-dotnet-sqldatabase/azure-app-in-browser.png)
 

articles/azure-government/documentation-government-impact-level-5.md

@@ -139,7 +139,7 @@ Azure HDInsight can be used in Azure Government supporting Impact Level 5 worklo
 
 Azure SQL Warehouse can be used in Azure Government supporting Impact Level 5 workloads in the following configurations:
 
-- Add Transparent Data Encryption with customer managed keys via Azure Key Vault (additional documentation and guidance found in the documentation for [Azure SQL transparent data encryption](../sql-database/transparent-data-encryption-byok-azure-sql.md)).
+- Add Transparent Data Encryption with customer managed keys via Azure Key Vault (additional documentation and guidance found in the documentation for [Azure SQL transparent data encryption](../azure-sql/database/transparent-data-encryption-byok-overview.md)).
 
 > [!NOTE]
 > The instructions to enable this are the same as for Azure SQL database.
@@ -747,7 +747,7 @@ To help ensure the security and integrity of data moved to the cloud, StorSimple
 
 Azure SQL Database can be used in Azure Government supporting Impact Level 5 workloads in the following configurations:
 
-- Add Transparent Data Encryption with customer managed keys via Azure Key Vault (additional documentation and guidance found in the [Azure SQL documentation](../sql-database/transparent-data-encryption-byok-azure-sql.md)).
+- Add Transparent Data Encryption with customer managed keys via Azure Key Vault (additional documentation and guidance found in the [Azure SQL documentation](../azure-sql/database/transparent-data-encryption-byok-overview.md)).
 
 | **Service** | **USGov VA** | **USGov IA** | **USGov TX** | **USGov AZ** | **USDoD East** | **USDoD Cent** |
 | --- | --- | --- | --- | --- | --- | --- |
@@ -757,7 +757,7 @@ Azure SQL Database can be used in Azure Government supporting Impact Level 5 wor
 
 Azure SQL Stretch Database can be used in Azure Government supporting Impact Level 5 workloads in the following configurations:
 
-- Add Transparent Data Encryption with customer managed keys via Azure Key Vault (additional documentation and guidance found in the documentation for [Azure SQL transparent data encryption](../sql-database/transparent-data-encryption-byok-azure-sql.md)).
+- Add Transparent Data Encryption with customer managed keys via Azure Key Vault (additional documentation and guidance found in the documentation for [Azure SQL transparent data encryption](../azure-sql/database/transparent-data-encryption-byok-overview.md)).
 
 | **Service** | **USGov VA** | **USGov IA** | **USGov TX** | **USGov AZ** | **USDoD East** | **USDoD Cent** |
 | --- | --- | --- | --- | --- | --- | --- |

articles/azure-sql/database/aad-authentication-configure.md

@@ -15,7 +15,7 @@ ms.date: 03/27/2020
 ---
 # Configure and manage Azure Active Directory authentication with SQL
 
-This article shows you how to create and populate Azure AD, and then use Azure AD with [Azure SQL Database](../../sql-database/sql-database-technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md). For an overview, see [Azure Active Directory Authentication](aad-authentication-overview.md).
+This article shows you how to create and populate Azure AD, and then use Azure AD with [Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md). For an overview, see [Azure Active Directory Authentication](aad-authentication-overview.md).
 
 ## Azure AD authentication methods
 

articles/azure-sql/database/aad-authentication-overview.md

@@ -14,7 +14,7 @@ ms.date: 04/23/2020
 ---
 # Use Azure Active Directory Authentication for authentication with Azure SQL
 
-Azure Active Directory authentication is a mechanism of connecting to [Azure SQL Database](../../sql-database/sql-database-technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) by using identities in Azure Active Directory (Azure AD).
+Azure Active Directory authentication is a mechanism of connecting to [Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) by using identities in Azure Active Directory (Azure AD).
 
 > [!NOTE]
 > This article applies to Azure SQL Database, SQL Managed Instance, and Azure Synapse. For simplicity, Azure SQL is used when referring to all three.

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

@@ -35,7 +35,7 @@ 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](dtu-service-tiers.md) and [vCore-based purchasing model](../../sql-database/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](dtu-service-tiers.md) and [vCore-based purchasing model](service-tiers-vcore.md).
 After the secondary is created and seeded, data begins replicating from the primary database to the new secondary database.
 
 > [!NOTE]

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

@@ -122,7 +122,7 @@ Transaction log rate throttling on the primary due to lower compute size on a se
 > [!NOTE]
 > Transaction log rate on the primary may be throttled for reasons unrelated to lower compute size on a secondary. This kind of throttling may occur even if the secondary has the same or higher compute size than the primary. For details, including wait types for different kinds of log rate throttling, see [Transaction log rate governance](resource-limits-logical-server.md#transaction-log-rate-governance).
 
-For more information on the SQL Database compute sizes, see [What are SQL Database Service Tiers](../../sql-database/sql-database-purchase-models.md).
+For more information on the SQL Database compute sizes, see [What are SQL Database Service Tiers](purchasing-models.md).
 
 ## Cross-subscription geo-replication
 
@@ -288,5 +288,5 @@ As discussed previously, active geo-replication can also be managed programmatic
 - SQL Database also supports auto-failover groups. For more information, see using [auto-failover groups](auto-failover-group-overview.md).
 - For a business continuity overview and scenarios, see [Business continuity overview](business-continuity-high-availability-disaster-recover-hadr-overview.md)
 - To learn about Azure SQL Database automated backups, see [SQL Database automated backups](automated-backups-overview.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 using automated backups for recovery, see [Restore a database from the service-initiated backups](recovery-using-backups.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/advanced-data-security.md

@@ -22,8 +22,8 @@ Advanced data security (ADS) is a unified package for advanced SQL security capa
 Advanced data security (ADS) provides a set of advanced SQL security capabilities, including data discovery & classification, vulnerability assessment, and Advanced Threat Protection.
 
 - [Data Discovery & Classification](data-discovery-and-classification-overview.md) provides capabilities built into Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse for discovering, classifying, labeling & reporting the sensitive data in your databases. It can be used to provide visibility into your database classification state, and to track the access to sensitive data within the database and beyond its borders.
-- [Vulnerability Assessment](../../sql-database/sql-vulnerability-assessment.md) is an easy to configure service that can discover, track, and help you remediate potential database vulnerabilities. It provides visibility into your security state, and includes actionable steps to resolve security issues, and enhance your database fortifications.
-- [Advanced Threat Protection](../../sql-database/sql-database-threat-detection-overview.md) detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit your database. It continuously monitors your database for suspicious activities, and provides immediate security alerts on potential vulnerabilities, SQL injection attacks, and anomalous database access patterns. Advanced Threat Protection alerts provide details of the suspicious activity and recommend action on how to investigate and mitigate the threat.
+- [Vulnerability Assessment](sql-vulnerability-assessment.md) is an easy to configure service that can discover, track, and help you remediate potential database vulnerabilities. It provides visibility into your security state, and includes actionable steps to resolve security issues, and enhance your database fortifications.
+- [Advanced Threat Protection](threat-detection-overview.md) detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit your database. It continuously monitors your database for suspicious activities, and provides immediate security alerts on potential vulnerabilities, SQL injection attacks, and anomalous database access patterns. Advanced Threat Protection alerts provide details of the suspicious activity and recommend action on how to investigate and mitigate the threat.
 
 Enable SQL ADS once to enable all of these included features. With one click, you can enable ADS for all databases on your [server](logical-servers.md) in Azure (which hosts SQL Database or Azure Synapse Analytics) or in you instance in Azure SQL Managed Instance. Enabling or managing ADS settings requires belonging to the [SQL security manager](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#sql-security-manager) role, SQL database admin role or SQL server admin role.
 
@@ -70,6 +70,6 @@ Advanced data security settings for your server or managed instance can also be
 ## Next steps
 
 - Learn more about [Data Discovery & Classification](data-discovery-and-classification-overview.md)
-- Learn more about [vulnerability Assessment](../../sql-database/sql-vulnerability-assessment.md)
-- Learn more about [Advanced Threat Protection](../../sql-database/sql-database-threat-detection.md)
+- Learn more about [vulnerability Assessment](sql-vulnerability-assessment.md)
+- Learn more about [Advanced Threat Protection](threat-detection.md)
 - Learn more about [Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-intro)

articles/sql-database/sql-database-resource-manager-samples.md renamed to articles/azure-sql/database/arm-templates-content-guide.md

@@ -25,7 +25,7 @@ For example, for database `Database1` on `Server1` the following is a possible v
 
     Server1/Database1/SqlDbAuditing_ServerAudit_NoRetention/2019-02-03/12_23_30_794_0.xel
 
-[Read-only Replicas](../../sql-database/sql-database-read-scale-out.md) Audit logs are stored in the same container. The directory hierarchy within the container is of the form `<ServerName>/<DatabaseName>/<AuditName>/<Date>/RO/`. The Blob filename shares the same format. The Audit Logs of Read-only Replicas are stored in the same container.
+[Read-only Replicas](read-scale-out.md) Audit logs are stored in the same container. The directory hierarchy within the container is of the form `<ServerName>/<DatabaseName>/<AuditName>/<Date>/RO/`. The Blob filename shares the same format. The Audit Logs of Read-only Replicas are stored in the same container.
 
 
 ### Event Hub