fixing things

azure-sql/database/develop-cplusplus-simple.md

@@ -131,7 +131,7 @@ You can find the GetStarted solution that contains all the samples in this artic
 
 ## Next steps
 
-* Review the [SQL Database Development Overview](../../synapse-analytics/sql/develop-overview.md)
+* Review the [SQL Database Development Overview](develop-overview.md)
 * More information on the [ODBC API Reference](https://docs.microsoft.com/sql/odbc/reference/syntax/odbc-api-reference/)
 
 ## Additional resources

azure-sql/database/doc-changes-updates-release-notes.md

@@ -64,9 +64,9 @@ The following features are enabled in SQL Managed Instance deployment model in H
   - Support for subscriptions with <a href="https://aka.ms/sql-mi-visual-studio-subscribers"> Azure monthly credit for Visual Studio subscribers </a> and increased [regional limits](../../sql-database/sql-database-managed-instance-resource-limits.md#regional-resource-limitations).
   - Support for <a href="https://docs.microsoft.com/sharepoint/administration/deploy-azure-sql-managed-instance-with-sharepoint-servers-2016-2019"> SharePoint 2016 and SharePoint 2019 </a> and <a href="https://docs.microsoft.com/business-applications-release-notes/october18/dynamics365-business-central/support-for-azure-sql-database-managed-instance"> Dynamics 365 Business Central </a>
   - Create SQL Managed Instances with <a href="https://aka.ms/managed-instance-collation">instance-level collation</a> and <a href="https://azure.microsoft.com/updates/managed-instance-time-zone-ga/">time-zone</a> of your choice.
-  - SQL Managed instances are now protected with <a href="sql-database-managed-instance-management-endpoint-verify-built-in-firewall.md">built-in firewall</a>.
+  - SQL Managed instances are now protected with [built-in firewall](../../sql-database/sql-database-managed-instance-management-endpoint-verify-built-in-firewall.md).
   - Configure SQL Managed Instances to use [public endpoints](../../sql-database/sql-database-managed-instance-public-endpoint-configure.md), [Proxy override](connectivity-architecture.md#connection-policy) connection to get better network performance, <a href="https://aka.ms/four-cores-sql-mi-update"> 4 vCores on Gen5 hardware generation</a> or <a href="https://aka.ms/managed-instance-configurable-backup-retention">Configure backup retention up to 35 days</a> for Point-in-time restore. [Long-term backup retention](long-term-retention-overview.md#managed-instance-support) (up to 10 years) is currently in limited public preview.  
-  - New functionalities enable you to <a href="https://medium.com/@jocapc/geo-restore-your-databases-on-azure-sql-instances-1451480e90fa">geo-restore your database to another data center using PowerShell</a>, [rename database](https://azure.microsoft.com/updates/azure-sql-database-managed-instance-database-rename-is-supported/), [delete virtual cluster](sql-database-managed-instance-delete-virtual-cluster.md).
+  - New functionalities enable you to <a href="https://medium.com/@jocapc/geo-restore-your-databases-on-azure-sql-instances-1451480e90fa">geo-restore your database to another data center using PowerShell</a>, [rename database](https://azure.microsoft.com/updates/azure-sql-database-managed-instance-database-rename-is-supported/), [delete virtual cluster](../../sql-database/sql-database-managed-instance-delete-virtual-cluster.md).
   - New built-in [Instance Contributor role](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#sql-managed-instance-contributor) enables separation of duty (SoD) compliance with security principles and compliance with enterprise standards.
   - SQL Managed Instance is available in the following Azure Government regions to GA (US Gov Texas, US Gov Arizona) as well as in China North 2 and China East 2. It is also available in the following public regions: Australia Central, Australia Central 2, Brazil South, France South, UAE Central, UAE North, South Africa North, South Africa West.
 

azure-sql/database/monitor-tune-overview.md

@@ -20,7 +20,7 @@ Azure SQL Database provides a number of Database Advisors to provide intelligent
 
 Azure SQL Database and Azure SQL Managed Instance provide advanced monitoring and tuning capabilities backed by artificial intelligence to assist you in troubleshooting and maximizing the performance of your databases and solutions. You can choose to configure the [streaming export](configure-streaming-export-metrics-diagnostic-telemtry-logging.md) of these [Intelligent Insights](../../sql-database/sql-database-intelligent-insights.md) and other database resource logs and metrics to one of several destinations for consumption and analysis, particularly using [SQL Analytics](../../azure-monitor/insights/azure-sql.md)). Azure SQL Analytics is an advanced cloud monitoring solution for monitoring performance of all of your Azure SQL databases at scale and across multiple subscriptions in a single view. For a list of the logs and metrics that you can export, see [diagnostic telemetry for export](configure-streaming-export-metrics-diagnostic-telemtry-logging.md#diagnostic-telemetry-for-export)
 
-Finally, SQL has its own monitoring and diagnostic capabilities with [SQL Server Query Store](https://docs.microsoft.com/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store) and [dynamic management views (DMVs)](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/system-dynamic-management-views). See [Monitoring using DMVs](../azure-sql/database/monitoring-with-dmvs.md) for scripts to monitor for a variety of performance issues.
+Finally, SQL has its own monitoring and diagnostic capabilities with [SQL Server Query Store](https://docs.microsoft.com/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store) and [dynamic management views (DMVs)](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/system-dynamic-management-views). See [Monitoring using DMVs](monitoring-with-dmvs.md) for scripts to monitor for a variety of performance issues.
 
 ## Monitoring and tuning capabilities in the Azure portal
 
@@ -34,7 +34,7 @@ You can quickly monitor a variety of resource metrics in the Azure portal in the
 
 ### Database advisors in Azure SQL Database
 
-Azure SQL Database includes [database advisors](database-advisor-implement-performance-recommendations.md) that provide performance tuning recommendations for single and pooled databases. These recommendations are available in the Azure portal as well as by using [PowerShell](https://docs.microsoft.com/powershell/module/az.sql/get-azsqldatabaseadvisor). You can also enable [automatic tuning](../azure-sql/database/automatic-tuning-overview.md) so that Azure SQL Database can automatically implement these tuning recommendations.
+Azure SQL Database includes [database advisors](database-advisor-implement-performance-recommendations.md) that provide performance tuning recommendations for single and pooled databases. These recommendations are available in the Azure portal as well as by using [PowerShell](https://docs.microsoft.com/powershell/module/az.sql/get-azsqldatabaseadvisor). You can also enable [automatic tuning](automatic-tuning-overview.md) so that Azure SQL Database can automatically implement these tuning recommendations.
 
 ### Query Performance Insight in Azure SQL Database
 
@@ -84,7 +84,7 @@ Stream metrics and resource logs to [Azure Storage](../../azure-monitor/platform
 
 ## Use extended events in the SQL database engine
 
-Additionally, you can use [extended events](https://docs.microsoft.com/sql/relational-databases/extended-events/extended-events) in SQL for additional advanced monitoring and troubleshooting. The extended events architecture enables users to collect as much or as little data as is necessary to troubleshoot or identify a performance problem. For information about using extended events in Azure SQL Database, see [Extended events in Azure SQL Database](../azure-sql/database/xevent-db-diff-from-svr.md).
+Additionally, you can use [extended events](https://docs.microsoft.com/sql/relational-databases/extended-events/extended-events) in SQL for additional advanced monitoring and troubleshooting. The extended events architecture enables users to collect as much or as little data as is necessary to troubleshoot or identify a performance problem. For information about using extended events in Azure SQL Database, see [Extended events in Azure SQL Database](xevent-db-diff-from-svr.md).
 
 ## Next steps
 

azure-sql/database/purchasing-models.md

@@ -71,7 +71,7 @@ The vCore-based purchasing model lets you independently choose compute and stora
 
 > [!IMPORTANT]
 > Compute resources, I/O, and data and log storage are charged per database or elastic pool. Backup storage is charged per each database. For more information about SQL Managed Instance charges, see [SQL Managed Instances](../../sql-database/sql-database-managed-instance.md).
-> **Region limitations:** For the current list of supported regions, see [products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=sql-database&regions=all). To create a SQL Managed Instance in a region that currently isn't supported, [send a support request via the Azure portal](../azure-sql/database/quota-increase-request.md).
+> **Region limitations:** For the current list of supported regions, see [products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=sql-database&regions=all). To create a SQL Managed Instance in a region that currently isn't supported, [send a support request via the Azure portal](quota-increase-request.md).
 
 If your Azure SQL Database consumes more than 300 DTUs, converting to the vCore-based purchasing model might reduce your costs. You can convert by using your API of choice or by using the Azure portal, with no downtime. However, conversion isn't required and isn't done automatically. If the DTU-based purchasing model meets your performance and business requirements, you should continue using it.
 
@@ -95,7 +95,7 @@ In the DTU-based purchasing model, you can choose between the basic, standard, a
 
 For a single database at a specific compute size within a [service tier](single-database-scale.md), Azure guarantees a certain level of resources for that database (independent of any other database in the Azure cloud). This guarantee provides a predictable level of performance. The amount of resources allocated for a database is calculated as a number of DTUs and is a bundled measure of compute, storage, and I/O resources.
 
-The ratio among these resources is originally determined by an [online transaction processing (OLTP) benchmark workload](sql-database-benchmark-overview.md) designed to be typical of real-world OLTP workloads. When your workload exceeds the amount of any of these resources, your throughput is throttled, resulting in slower performance and time-outs.
+The ratio among these resources is originally determined by an [online transaction processing (OLTP) benchmark workload](dtu-service-tiers.md) designed to be typical of real-world OLTP workloads. When your workload exceeds the amount of any of these resources, your throughput is throttled, resulting in slower performance and time-outs.
 
 The resources used by your workload don't impact the resources available to other SQL Databases in the Azure cloud. Likewise, the resources used by other workloads don't impact the resources available to your SQL Database.
 

azure-sql/database/reserved-capacity-overview.md

@@ -19,7 +19,7 @@ Save money with Azure SQL Database and SQL Managed Instance by committing to a r
 
 You do not need to assign the reservation to specific SQL Database, or SQL Managed Instance.  Matching existing deployments that are already running or ones that are newly deployed, will automatically get the benefit. By purchasing a reservation, you commit to usage for the compute costs for a period of one or three years. As soon as you buy a reservation, the compute charges that match the reservation attributes are no longer charged at the pay-as-you go rates. A reservation does not cover software, networking, or storage charges associated with the service. At the end of the reservation term, the billing benefit expires and the SQL Database or SQL Managed Instance are billed at the pay-as-you go price. Reservations do not auto-renew. For pricing information, see the [reserved capacity offering](https://azure.microsoft.com/pricing/details/sql-database/managed/).
 
-You can buy reserved capacity in the [Azure portal](https://portal.azure.com). Pay for the reservation [up front or with monthly payments](../cost-management-billing/reservations/monthly-payments-reservations.md). To buy reserved capacity:
+You can buy reserved capacity in the [Azure portal](https://portal.azure.com). Pay for the reservation [up front or with monthly payments](../../cost-management-billing/reservations/prepare-buy-reservation.md). To buy reserved capacity:
 
 - You must be in the owner role for at least one Enterprise or individual subscription with pay-as-you-go rates.
 - For Enterprise subscriptions, **Add Reserved Instances** must be enabled in the [EA portal](https://ea.azure.com). Or, if that setting is disabled, you must be an EA Admin on the subscription. reserved capacity.

azure-sql/database/security-best-practice.md

@@ -22,7 +22,7 @@ This document provides guidance on how to solve common security requirements for
 
 ### Azure SQL Database deployment offers covered in this guide
 
-- [Azure SQL Databases](https://docs.microsoft.com/azure/sql-database/sql-database-single-index): [single databases](../azure-sql/database/single-database-overview.md) and [elastic pools](elastic-pool-overview.md) in [servers](logical-servers.md)
+- [Azure SQL Databases](https://docs.microsoft.com/azure/sql-database/sql-database-single-index): [single databases](single-database-overview.md) and [elastic pools](elastic-pool-overview.md) in [servers](logical-servers.md)
 - [Azure SQL Managed Instances](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-index)
 
 ### SQL deployment offers not covered in this guide
@@ -123,7 +123,7 @@ Azure Multi-Factor Authentication (MFA) helps provides additional security by re
 **Best practices**:
 
 - Activate Conditional Access in Azure AD (requires Premium subscription).
-  - See the article, [Conditional Access in Azure AD](../active-directory/conditional-access/overview.md).  
+  - See the article, [Conditional Access in Azure AD](../../active-directory/conditional-access/overview.md).  
 
 - Create Azure AD group(s) and enable MFA policy for selected groups using Azure AD Conditional Access.
   - See the article, [Plan Conditional Access Deployment](../../active-directory/conditional-access/plan-conditional-access.md).
@@ -169,7 +169,7 @@ Password-based authentication methods are a weaker form of authentication. Crede
 
 **Best practices**:
 
-- Use [managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md).
+- Use [managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md).
   - [System-assigned managed identity](../../active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-sql.md)
   - [User-assigned managed identity](../../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal.md)
   - [Use Azure SQL Database from app service with managed identity (without code changes)](https://github.com/Azure-Samples/app-service-msi-entityframework-dotnet)
@@ -545,7 +545,7 @@ In a SQL Managed Instance:
   - For an instance in SQL Managed Instance, use Network Security Groups (NSG) to restrict access over port 3342 only to required resources. For more information, see [Use an Azure SQL Managed Instance securely with public endpoints](../../sql-database/sql-database-managed-instance-public-endpoint-securely.md).
 
 > [!NOTE]
-> A SQL Managed Instance public endpoint is not enabled by default and it and must be explicitly enabled. If company policy disallows the use of public endpoints, use [Azure Policy](../governance/policy/overview.md) to prevent enabling public endpoints in the first place.
+> A SQL Managed Instance public endpoint is not enabled by default and it and must be explicitly enabled. If company policy disallows the use of public endpoints, use [Azure Policy](../../governance/policy/overview.md) to prevent enabling public endpoints in the first place.
 
 - Set up Azure Networking components:
   - Follow [Azure best practices for network security](../../security/fundamentals/network-best-practices.md).
@@ -576,17 +576,17 @@ In a SQL Managed Instance:
 
 - For Web App with ASE or VNet Integrated Web App connecting to a database in SQL Database, you can use [VNet Service endpoints and VNet Firewall Rules](vnet-service-endpoint-rule-overview.md) to limit access from a specific VNet and subnet. Then set **Allow Azure Services** to OFF. You can also connect ASE to a managed instance in SQL Managed Instance over a private data path.  
 
-- Ensure that your Web App is configured per the article, [Best practices for securing PaaS web and mobile applications using Azure App Service](../security/security-paas-applications-using-app-services.md).
+- Ensure that your Web App is configured per the article, [Best practices for securing PaaS web and mobile applications using Azure App Service](../../security/fundamentals/paas-applications-using-app-services.md).
 
-- Install [Web Application Firewall (WAF)](../application-gateway/waf-overview.md) to protect your web app from common exploits and vulnerabilities.
+- Install [Web Application Firewall (WAF)](../../web-application-firewall/ag/ag-overview.md) to protect your web app from common exploits and vulnerabilities.
 
 ### Configure Azure VM hosting for secure connections to SQL Database/SQL Managed Instance
 
 **Best practices**:
 
 - Use a combination of Allow and Deny rules on the NSGs of Azure VMs to control which regions can be accessed from the VM.
 
-- Ensure that your VM is configured per the article, [Security best practices for IaaS workloads in Azure](../security/azure-security-iaas.md).
+- Ensure that your VM is configured per the article, [Security best practices for IaaS workloads in Azure](../../security/fundamentals/iaas.md).
 
 - Ensure that all VMs are associated with a specific VNet and subnet.