diff --git a/azure-sql/database/develop-cplusplus-simple.md b/azure-sql/database/develop-cplusplus-simple.md index 47f5b0a6a11..603a26586ae 100644 --- a/azure-sql/database/develop-cplusplus-simple.md +++ b/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 diff --git a/azure-sql/database/doc-changes-updates-release-notes.md b/azure-sql/database/doc-changes-updates-release-notes.md index d01dca4d9b5..a53382ef160 100644 --- a/azure-sql/database/doc-changes-updates-release-notes.md +++ b/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 Azure monthly credit for Visual Studio subscribers and increased [regional limits](../../sql-database/sql-database-managed-instance-resource-limits.md#regional-resource-limitations). - Support for SharePoint 2016 and SharePoint 2019 and Dynamics 365 Business Central - Create SQL Managed Instances with instance-level collation and time-zone of your choice. - - SQL Managed instances are now protected with built-in firewall. + - 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, 4 vCores on Gen5 hardware generation or Configure backup retention up to 35 days 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 geo-restore your database to another data center using PowerShell, [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 geo-restore your database to another data center using PowerShell, [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. diff --git a/azure-sql/database/media/configure-streaming-export-metrics-diagnostic-telemtry-logging/architecture.png b/azure-sql/database/media/configure-streaming-export-metrics-diagnostic-telemtry-logging/architecture.png new file mode 100644 index 00000000000..db0153bbee4 Binary files /dev/null and b/azure-sql/database/media/configure-streaming-export-metrics-diagnostic-telemtry-logging/architecture.png differ diff --git a/azure-sql/database/monitor-tune-overview.md b/azure-sql/database/monitor-tune-overview.md index fa832b32e37..1605ff9d1b6 100644 --- a/azure-sql/database/monitor-tune-overview.md +++ b/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 diff --git a/azure-sql/database/purchasing-models.md b/azure-sql/database/purchasing-models.md index 77eae05dd78..252a3554113 100644 --- a/azure-sql/database/purchasing-models.md +++ b/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®ions=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®ions=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. diff --git a/azure-sql/database/reserved-capacity-overview.md b/azure-sql/database/reserved-capacity-overview.md index bc15ef9830b..0a39dff54e6 100644 --- a/azure-sql/database/reserved-capacity-overview.md +++ b/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. diff --git a/azure-sql/database/security-best-practice.md b/azure-sql/database/security-best-practice.md index 0b378ba1d1a..8507b037d40 100644 --- a/azure-sql/database/security-best-practice.md +++ b/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,9 +576,9 @@ 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 @@ -586,7 +586,7 @@ In a SQL Managed Instance: - 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. diff --git a/azure-sql/database/security-overview.md b/azure-sql/database/security-overview.md index 907b062f312..0142d35fc27 100644 --- a/azure-sql/database/security-overview.md +++ b/azure-sql/database/security-overview.md @@ -29,7 +29,7 @@ IP firewall rules grant access to databases based on the originating IP address ### Virtual network firewall rules -[Virtual network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md) extend your virtual network connectivity over the Azure backbone and enable Azure SQL Database to identify the virtual network subnet that traffic originates from. To allow traffic to reach Azure SQL Database, use the SQL [service tags](../virtual-network/security-overview.md) to allow outbound traffic through Network Security Groups. +[Virtual network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md) extend your virtual network connectivity over the Azure backbone and enable Azure SQL Database to identify the virtual network subnet that traffic originates from. To allow traffic to reach Azure SQL Database, use the SQL [service tags](../../virtual-network/security-overview.md) to allow outbound traffic through Network Security Groups. [Virtual network rules](vnet-service-endpoint-rule-overview.md) enable Azure SQL Database to only accept communications that are sent from selected subnets inside a virtual network. @@ -39,7 +39,7 @@ IP firewall rules grant access to databases based on the originating IP address ## Access management > [!IMPORTANT] -> Managing databases and servers within Azure is controlled by your portal user account's role assignments. For more information on this article, see [Role-based access control in Azure portal](../role-based-access-control/overview.md). +> Managing databases and servers within Azure is controlled by your portal user account's role assignments. For more information on this article, see [Role-based access control in Azure portal](../../role-based-access-control/overview.md). ### Authentication @@ -58,7 +58,7 @@ Authentication is the process of proving the user is who they claim to be. Azure Additional Azure AD authentication options available are [Active Directory Universal Authentication for SQL Server Management Studio](../../sql-database/sql-database-ssms-mfa-authentication.md) connections including [Multi-Factor Authentication](../../active-directory/authentication/concept-mfa-howitworks.md) and [Conditional Access](conditional-access-confugre.md). > [!IMPORTANT] -> Managing databases and servers within Azure is controlled by your portal user account's role assignments. For more information on this article, see [Role-based access control in Azure portal](../role-based-access-control/overview.md). Controlling access with firewall rules does *not* apply to **a SQL Managed Instance**. Please see the following article on [connecting to a managed instance](../../sql-database/sql-database-managed-instance-connect-app.md) for more information about the networking configuration needed. +> Managing databases and servers within Azure is controlled by your portal user account's role assignments. For more information on this article, see [Role-based access control in Azure portal](../../role-based-access-control/overview.md). Controlling access with firewall rules does *not* apply to **a SQL Managed Instance**. Please see the following article on [connecting to a managed instance](../../sql-database/sql-database-managed-instance-connect-app.md) for more information about the networking configuration needed. ## Authorization @@ -117,7 +117,7 @@ In Azure, all newly created databases are encrypted by default and the database ![azure-database-ae.png](./media/security-overview/azure-database-ae.png) -[Always Encrypted](/sql/relational-databases/security/encryption/always-encrypted-database-engine) is a feature designed to protect sensitive data stored in specific database columns from access (for example, credit card numbers, national identification numbers, or data on a _need to know_ basis). This includes database administrators or other privileged users who are authorized to access the database to perform management tasks, but have no business need to access the particular data in the encrypted columns. The data is always encrypted, which means the encrypted data is decrypted only for processing by client applications with access to the encryption key. The encryption key is never exposed to SQL and can be stored either in the [Windows Certificate Store](../azure-sql/database/always-encrypted-certificate-store-configure.md) or in [Azure Key Vault](always-encrypted-azure-key-vault-configure.md). +[Always Encrypted](/sql/relational-databases/security/encryption/always-encrypted-database-engine) is a feature designed to protect sensitive data stored in specific database columns from access (for example, credit card numbers, national identification numbers, or data on a _need to know_ basis). This includes database administrators or other privileged users who are authorized to access the database to perform management tasks, but have no business need to access the particular data in the encrypted columns. The data is always encrypted, which means the encrypted data is decrypted only for processing by client applications with access to the encryption key. The encryption key is never exposed to SQL and can be stored either in the [Windows Certificate Store](always-encrypted-certificate-store-configure.md) or in [Azure Key Vault](always-encrypted-azure-key-vault-configure.md). ### Dynamic data masking diff --git a/azure-sql/database/service-tiers-vcore.md b/azure-sql/database/service-tiers-vcore.md index 13d79ea19c4..bcba52834b9 100644 --- a/azure-sql/database/service-tiers-vcore.md +++ b/azure-sql/database/service-tiers-vcore.md @@ -28,9 +28,9 @@ Service tier options in the vCore model include General Purpose, Business Critic |---|---|---|---| |Best for|Most business workloads. Offers budget-oriented, balanced, and scalable compute and storage options. |Offers business applications the highest resilience to failures by using several isolated replicas, and provides the highest I/O performance per database replica.|Most business workloads with highly scalable storage and read-scale requirements. Offers higher resilience to failures by allowing configuration of more than one isolated database replica. | |Storage|Uses remote storage.
**SQL Database provisioned compute**:
5 GB – 4 TB
**Serverless compute**:
5 GB - 3 TB
**SQL Managed Instance**: 32 GB - 8 TB |Uses local SSD storage.
**SQL Database provisioned compute**:
5 GB – 4 TB
**SQL Managed Instance**:
32 GB - 4 TB |Flexible autogrow of storage as needed. Supports up to 100 TB of storage. Uses local SSD storage for local buffer-pool cache and local data storage. Uses Azure remote storage as final long-term data store. | -|IOPS and throughput (approximate)|**SQL Database**: See resource limits for [single databases](resource-limits-vcore-single-databases.md) and [elastic pools](resource-limits-vcore-elastic-pools.md).
**SQL Managed Instance**: See [Overview Azure SQL Managed Instance resource limits](../../sql-database/../../sql-database/sql-database-managed-instance-resource-limits.md#service-tier-characteristics).|See resource limits for [single databases](resource-limits-vcore-single-databases.md) and [elastic pools](resource-limits-vcore-elastic-pools.md).|Hyperscale is a multi-tiered architecture with caching at multiple levels. Effective IOPS and throughput will depend on the workload.| +|IOPS and throughput (approximate)|**SQL Database**: See resource limits for [single databases](resource-limits-vcore-single-databases.md) and [elastic pools](resource-limits-vcore-elastic-pools.md).
**SQL Managed Instance**: See [Overview Azure SQL Managed Instance resource limits](../../sql-database/sql-database-managed-instance-resource-limits.md#service-tier-characteristics).|See resource limits for [single databases](resource-limits-vcore-single-databases.md) and [elastic pools](resource-limits-vcore-elastic-pools.md).|Hyperscale is a multi-tiered architecture with caching at multiple levels. Effective IOPS and throughput will depend on the workload.| |Availability|1 replica, no read-scale replicas|3 replicas, 1 [read-scale replica](read-scale-out.md),
zone-redundant high availability (HA)|1 read-write replica, plus 0-4 [read-scale replicas](read-scale-out.md)| -|Backups|[Read-access geo-redundant storage (RA-GRS)](../storage/common/storage-designing-ha-apps-with-ragrs.md), 7-35 days (7 days by default)|[RA-GRS](../storage/common/storage-designing-ha-apps-with-ragrs.md), 7-35 days (7 days by default)|Snapshot-based backups in Azure remote storage. Restores use these snapshots for fast recovery. Backups are instantaneous and don't impact compute I/O performance. Restores are fast and aren't a size-of-data operation (taking minutes rather than hours or days).| +|Backups|[Read-access geo-redundant storage (RA-GRS)](../../storage/common/geo-redundant-design.md), 7-35 days (7 days by default)|[RA-GRS](../..//storage/common/geo-redundant-design.md), 7-35 days (7 days by default)|Snapshot-based backups in Azure remote storage. Restores use these snapshots for fast recovery. Backups are instantaneous and don't impact compute I/O performance. Restores are fast and aren't a size-of-data operation (taking minutes rather than hours or days).| |In-memory|Not supported|Supported|Not supported| ||| @@ -101,7 +101,7 @@ To enable M-series hardware for a subscription and region, a support request mus \* In the [sys.dm_user_db_resource_governance](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-user-db-resource-governor-azure-sql-database) dynamic management view, hardware generation for Gen5 databases using Intel SP-8160 (Skylake) processors appears as Gen6. Resource limits for all Gen5 databases are the same regardless of processor type (Broadwell or Skylake). -For more information on resource limits, see [Resource limits for single databases (vCore)](sql-database-vcore-resource-limits-single-databases.md), or [Resource limits for elastic pools (vCore)](sql-database-vcore-resource-limits-elastic-pools.md). +For more information on resource limits, see [Resource limits for single databases (vCore)](resource-limits-vcore-single-databases.md), or [Resource limits for elastic pools (vCore)](resource-limits-vcore-elastic-pools.md). ### Selecting a hardware generation @@ -225,7 +225,7 @@ For pricing details, see the [Azure SQL Database pricing page](https://azure.mic For details about the specific compute and storage sizes available in the general purpose and business critical service tiers, see: -- [vCore-based resource limits for Azure SQL Database](sql-database-vcore-resource-limits-single-databases.md). -- [vCore-based resource limits for pooled Azure SQL Database](sql-database-vcore-resource-limits-elastic-pools.md). +- [vCore-based resource limits for Azure SQL Database](resource-limits-vcore-single-databases.md). +- [vCore-based resource limits for pooled Azure SQL Database](resource-limits-vcore-elastic-pools.md). - [vCore-based resource limits for Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance-resource-limits.md). diff --git a/azure-sql/database/sql-vulnerability-assessment.md b/azure-sql/database/sql-vulnerability-assessment.md index e1dc55a6537..a5e36ae3b7f 100644 --- a/azure-sql/database/sql-vulnerability-assessment.md +++ b/azure-sql/database/sql-vulnerability-assessment.md @@ -53,7 +53,7 @@ The following steps implement the vulnerability assessment: 1. Then click **Select Storage** on the **Vulnerability Assessment** pane to open the Vulnerability Assessment settings pane for either the entire server or managed instance. -1. Configure a storage account where your scan results for all databases on the server or managed instance will be stored. For information about storage accounts, see [About Azure storage accounts](../storage/common/storage-create-storage-account.md). After storage is configured, select **Scan** to scan your database for vulnerabilities. +1. Configure a storage account where your scan results for all databases on the server or managed instance will be stored. For information about storage accounts, see [About Azure storage accounts](../../storage/common/storage-account-create.md). After storage is configured, select **Scan** to scan your database for vulnerabilities. ![Scan a database](./media/sql-vulnerability-assessment/pp_va_initialize.png) diff --git a/azure-sql/database/technical-overview.md b/azure-sql/database/technical-overview.md index 148e756fa80..82c861be457 100644 --- a/azure-sql/database/technical-overview.md +++ b/azure-sql/database/technical-overview.md @@ -20,7 +20,7 @@ Azure SQL Database is a fully managed Platform as a Service (PaaS) Database Engi With Azure SQL Database, you can create a highly available and high-performance data storage layer for the applications and solutions in Azure. SQL Database can be the right choice for a variety of modern cloud applications because it enables you to process both relational data and [non-relational structures](multi-model-features.md), such as graphs, JSON, spatial, and XML. -It's based on the latest stable version of the [Microsoft SQL Server database engine](https://docs.microsoft.com/sql/sql-server/sql-server-technical-documentation?toc=/azure/sql-database/toc.json). You can use advanced query processing features, such as [high-performance in-memory technologies](sql-database-in-memory.md) and [intelligent query processing](https://docs.microsoft.com/sql/relational-databases/performance/intelligent-query-processing?toc=/azure/sql-database/toc.json). In fact, the newest capabilities of SQL Server are released first to SQL Database, and then to SQL Server itself. You get the newest SQL Server capabilities with no overhead for patching or upgrading, tested across millions of databases. +It's based on the latest stable version of the [Microsoft SQL Server database engine](https://docs.microsoft.com/sql/sql-server/sql-server-technical-documentation?toc=/azure/sql-database/toc.json). You can use advanced query processing features, such as [high-performance in-memory technologies](../../sql-database/sql-database-in-memory.md) and [intelligent query processing](https://docs.microsoft.com/sql/relational-databases/performance/intelligent-query-processing?toc=/azure/sql-database/toc.json). In fact, the newest capabilities of SQL Server are released first to SQL Database, and then to SQL Server itself. You get the newest SQL Server capabilities with no overhead for patching or upgrading, tested across millions of databases. SQL Database enables you to easily define and scale performance within two different purchasing models: a [vCore-based purchasing model](service-tiers-vcore.md) and a [DTU-based purchasing model](dtu-service-tiers.md). SQL Database is a fully managed service that has built-in high availability, backups, and other common maintenance operations. Microsoft handles all patching and updating of the SQL and operating system code. You don't have to manage the underlying infrastructure. @@ -75,7 +75,7 @@ For many businesses and applications, being able to create single databases and With elastic pools, you don't need to focus on dialing database performance up and down as demand for resources fluctuates. The pooled databases consume the performance resources of the elastic pool as needed. Pooled databases consume but don't exceed the limits of the pool, so your cost remains predictable even if individual database usage doesn't. -You can [add and remove databases to the pool](sql-database-elastic-pool-manage-portal.md), scaling your app from a handful of databases to thousands, all within a budget that you control. You can also control the minimum and maximum resources available to databases in the pool, to ensure that no database in the pool uses all the pool resources, and that every pooled database has a guaranteed minimum amount of resources. To learn more about design patterns for software as a service (SaaS) applications that use elastic pools, see [Design patterns for multi-tenant SaaS applications with SQL Database](sql-database-design-patterns-multi-tenancy-saas-applications.md). +You can [add and remove databases to the pool](elastic-pool-overview.md), scaling your app from a handful of databases to thousands, all within a budget that you control. You can also control the minimum and maximum resources available to databases in the pool, to ensure that no database in the pool uses all the pool resources, and that every pooled database has a guaranteed minimum amount of resources. To learn more about design patterns for software as a service (SaaS) applications that use elastic pools, see [Design patterns for multi-tenant SaaS applications with SQL Database](../../sql-database/saas-tenancy-app-design-patterns.md). Scripts can help with monitoring and scaling elastic pools. For an example, see [Use PowerShell to monitor and scale a SQL elastic pool in Azure SQL Database](scripts/monitor-and-scale-pool-powershell.md). @@ -92,7 +92,7 @@ Azure SQL Database provides advanced monitoring and troubleshooting features tha - The built-in monitoring capabilities provided by the latest version of SQL Server Database Engine. They enable you to find real-time performance insights. - PaaS monitoring capabilities provided by Azure that enable you to monitor and troubleshoot a large number of database instances. -[Query Store](https://docs.microsoft.com/sql/relational-databases/performance/best-practice-with-the-query-store), a built-in SQL Server monitoring feature, records the performance of your queries in real time, and enables you to identify the potential performance issues and the top resource consumers. Automatic tuning and recommendations provide advice regarding the queries with the regressed performance and missing or duplicated indexes. Automatic tuning in SQL Database enables you to either manually apply the scripts that can fix the issues, or let SQL Database apply the fix. SQL Database can also test and verify that the fix provides some benefit, and retain or revert the change depending on the outcome. In addition to Query Store and automatic tuning capabilities, you can use standard [DMVs and XEvent](../azure-sql/database/monitoring-with-dmvs.md) to monitor the workload performance. +[Query Store](https://docs.microsoft.com/sql/relational-databases/performance/best-practice-with-the-query-store), a built-in SQL Server monitoring feature, records the performance of your queries in real time, and enables you to identify the potential performance issues and the top resource consumers. Automatic tuning and recommendations provide advice regarding the queries with the regressed performance and missing or duplicated indexes. Automatic tuning in SQL Database enables you to either manually apply the scripts that can fix the issues, or let SQL Database apply the fix. SQL Database can also test and verify that the fix provides some benefit, and retain or revert the change depending on the outcome. In addition to Query Store and automatic tuning capabilities, you can use standard [DMVs and XEvent](monitoring-with-dmvs.md) to monitor the workload performance. Azure provides [built-in performance monitoring](performance-guidance.md) and [alerting](alerts-insights-configure-portal.md) tools, combined with performance ratings, that enable you to monitor the status of thousands of databases. Using these tools, you can quickly assess the impact of scaling up or down, based on your current or projected performance needs. Additionally, SQL Database can [emit metrics and resource logs](configure-streaming-export-metrics-diagnostic-telemtry-logging.md) for easier monitoring. You can configure SQL Database to store resource usage, workers and sessions, and connectivity into one of these Azure resources: @@ -145,7 +145,7 @@ However, constantly monitoring a database is a hard and tedious task, especially Managing a huge number of databases might be impossible to do efficiently even with all available tools and reports that SQL Database and Azure provide. Instead of monitoring and tuning your database manually, you might consider delegating some of the monitoring and tuning actions to SQL Database by using [automatic tuning](automatic-tuning-overview.md). SQL Database automatically applies recommendations, tests, and verifies each of its tuning actions to ensure the performance keeps improving. This way, SQL Database automatically adapts to your workload in a controlled and safe way. Automatic tuning means that the performance of your database is carefully monitored and compared before and after every tuning action. If the performance doesn't improve, the tuning action is reverted. -Many of our partners that run [SaaS multi-tenant apps](sql-database-design-patterns-multi-tenancy-saas-applications.md) on top of SQL Database are relying on automatic performance tuning to make sure their applications always have stable and predictable performance. For them, this feature tremendously reduces the risk of having a performance incident in the middle of the night. In addition, because part of their customer base also uses SQL Server, they're using the same indexing recommendations provided by SQL Database to help their SQL Server customers. +Many of our partners that run [SaaS multi-tenant apps](../../sql-database/saas-tenancy-app-design-patterns.md) on top of SQL Database are relying on automatic performance tuning to make sure their applications always have stable and predictable performance. For them, this feature tremendously reduces the risk of having a performance incident in the middle of the night. In addition, because part of their customer base also uses SQL Server, they're using the same indexing recommendations provided by SQL Database to help their SQL Server customers. Two automatic tuning aspects are [available in SQL Database](automatic-tuning-overview.md): @@ -158,7 +158,7 @@ You can use [adaptive query processing](/sql/relational-databases/performance/in ## Advanced security and compliance -SQL Database provides a range of [built-in security and compliance features](../azure-sql/database/security-overview.md) to help your application meet various security and compliance requirements. +SQL Database provides a range of [built-in security and compliance features](security-overview.md) to help your application meet various security and compliance requirements. > [!IMPORTANT] > Microsoft has certified Azure SQL Database (all deployment options) against a number of compliance standards. For more information, see the [Microsoft Azure Trust Center](https://gallery.technet.microsoft.com/Overview-of-Azure-c1be3942), where you can find the most current list of SQL Database compliance certifications. @@ -206,7 +206,7 @@ SQL Database makes building and maintaining applications easier and more product A free, downloadable, open-source code editor for Windows, macOS, and Linux. It supports extensions, including the [mssql extension](https://aka.ms/mssql-marketplace) for querying Microsoft SQL Server, Azure SQL Database, and Azure SQL Data Warehouse. -SQL Database supports building applications with Python, Java, Node.js, PHP, Ruby, and .NET on macOS, Linux, and Windows. SQL Database supports the same [connection libraries](sql-database-libraries.md) as SQL Server. +SQL Database supports building applications with Python, Java, Node.js, PHP, Ruby, and .NET on macOS, Linux, and Windows. SQL Database supports the same [connection libraries](connect-query-content-reference-guide.md#libraries) as SQL Server. [!INCLUDE [sql-database-create-manage-portal](../../sql-database/includes/sql-database-create-manage-portal.md)] @@ -218,7 +218,7 @@ The current version of SQL Database is V12. Version V11 has been retired. ### Can I control when patching downtime occurs? -No. The impact of patching is generally not noticeable if you [employ retry logic](../../synapse-analytics/sql/develop-overview.md#resiliency) in your app. For more information, see [Planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md). +No. The impact of patching is generally not noticeable if you [employ retry logic](develop-overview.md#resiliency) in your app. For more information, see [Planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md). ### Azure Hybrid Benefit questions @@ -259,8 +259,8 @@ SQL Database customers have the following rights associated with Azure Hybrid Be - See these quickstarts to get started: - [Create a SQL database in the Azure portal](quickstart-create-single-database.md) - - [Create a SQL database with the Azure CLI](sql-database-get-started-cli.md) - - [Create a SQL database using PowerShell](sql-database-get-started-powershell.md) + - [Create a SQL database with the Azure CLI](az-cli-script-samples-content-guide.md) + - [Create a SQL database using PowerShell](powershell-script-content-guide.md) - For a set of Azure CLI and PowerShell samples, see: - [Azure CLI samples for SQL Database](az-cli-script-samples-content-guide.md) diff --git a/azure-sql/database/transparent-data-encryption-byok-configure.md b/azure-sql/database/transparent-data-encryption-byok-configure.md index 39325e74d13..212af8a2a29 100644 --- a/azure-sql/database/transparent-data-encryption-byok-configure.md +++ b/azure-sql/database/transparent-data-encryption-byok-configure.md @@ -36,7 +36,7 @@ This article walks through how to use a key from Azure Key Vault for Transparent For Az module installation instructions, see [Install Azure PowerShell](/powershell/azure/install-az-ps). For specific cmdlets, see [AzureRM.Sql](https://docs.microsoft.com/powershell/module/AzureRM.Sql/). -For specifics on Key Vault, see [PowerShell instructions from Key Vault](../key-vault/secrets/quick-create-powershell.md) and [How to use Key Vault soft-delete with PowerShell](../../key-vault/general/soft-delete-powershell.md). +For specifics on Key Vault, see [PowerShell instructions from Key Vault](../../key-vault/secrets/quick-create-powershell.md) and [How to use Key Vault soft-delete with PowerShell](../../key-vault/general/soft-delete-powershell.md). > [!IMPORTANT] > The PowerShell Azure Resource Manager (RM) module is still supported, but all future development is for the Az.Sql module. The AzureRM module will continue to receive bug fixes until at least December 2020. The arguments for the commands in the Az module and in the AzureRm modules are substantially identical. For more about their compatibility, see [Introducing the new Azure PowerShell Az module](/powershell/azure/new-azureps-module-az). diff --git a/azure-sql/database/transparent-data-encryption-byok-overview.md b/azure-sql/database/transparent-data-encryption-byok-overview.md index 8528d86fbf3..a04ffbf5495 100644 --- a/azure-sql/database/transparent-data-encryption-byok-overview.md +++ b/azure-sql/database/transparent-data-encryption-byok-overview.md @@ -176,7 +176,7 @@ Use the Backup-AzKeyVaultKey cmdlet to retrieve the key in encrypted format from ## Geo-DR and customer-managed TDE -In both [active geo-replication](active-geo-replication-overview.md) and [failover groups](sql-database-auto-failover-group.md) scenarios, each server involved requires a separate key vault, that must be co-located with the server in the same Azure region. Customer is responsible for keeping the key material across the key vaults consistent, so that geo-secondary is in sync and can take over using the same key from its local key vault if primary becomes inaccessible due to an outage in the region and a failover is triggered. Up to four secondaries can be configured, and chaining (secondaries of secondaries) is not supported. +In both [active geo-replication](active-geo-replication-overview.md) and [failover groups](auto-failover-group-overview.md) scenarios, each server involved requires a separate key vault, that must be co-located with the server in the same Azure region. Customer is responsible for keeping the key material across the key vaults consistent, so that geo-secondary is in sync and can take over using the same key from its local key vault if primary becomes inaccessible due to an outage in the region and a failover is triggered. Up to four secondaries can be configured, and chaining (secondaries of secondaries) is not supported. To avoid issues while establishing or during geo-replication due to incomplete key material, it's important to follow these rules when configuring customer-managed TDE: @@ -188,7 +188,7 @@ To avoid issues while establishing or during geo-replication due to incomplete k ![Failover groups and geo-dr](./media/transparent-data-encryption-byok-overview/customer-managed-tde-with-bcdr.png) -To test a failover, follow the steps in [Active geo-replication overview](sql-database-geo-replication-overview.md). It should be done on a regular basis to confirm the access permissions for SQL to both key vaults have been maintained. +To test a failover, follow the steps in [Active geo-replication overview](active-geo-replication-overview.md). It should be done on a regular basis to confirm the access permissions for SQL to both key vaults have been maintained. ## Next steps diff --git a/azure-sql/database/troubleshoot-common-errors-issues.md b/azure-sql/database/troubleshoot-common-errors-issues.md index fb656cdf30c..34a71946355 100644 --- a/azure-sql/database/troubleshoot-common-errors-issues.md +++ b/azure-sql/database/troubleshoot-common-errors-issues.md @@ -13,7 +13,7 @@ ms.date: 01/14/2020 # Troubleshooting connectivity issues and other errors with Azure SQL Database -You receive error messages when the connection to Azure SQL Database fails. These connection problems can be caused by Azure SQL Database reconfiguration, firewall settings, a connection timeout, incorrect login information or failure to apply best practices and design guidelines during the [application design](../../synapse-analytics/sql/develop-overview.md) process. Additionally, if the maximum limit on some Azure SQL Database resources is reached, you can't connect to Azure SQL Database. +You receive error messages when the connection to Azure SQL Database fails. These connection problems can be caused by Azure SQL Database reconfiguration, firewall settings, a connection timeout, incorrect login information or failure to apply best practices and design guidelines during the [application design](develop-overview.md) process. Additionally, if the maximum limit on some Azure SQL Database resources is reached, you can't connect to Azure SQL Database. ## Transient fault error messages (40197, 40613 and others)