Merge pull request #21837 from MicrosoftDocs/main

Sync from default branch

Author: MikeRayMSFT

.acrolinx-config.edn

@@ -1,2 +1,2 @@
 {:allowed-branchname-matches ["main" "release-.*" "sandbox-.*"]
- :allowed-filename-matches ["(?i)docs/(?:(?!toc.yml))" "docs-msdn"]}
+ :allowed-filename-matches ["(?i)docs/(?:(?!toc.yml))" "docs-msdn" "(?i)azure-sql/(?:(?!toc.yml))" "(?i)data-migration/(?:(?!toc.yml))"]}

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

@@ -10,7 +10,7 @@ ms.subservice: service-overview
 ms.custom: sqldbrb=2, references_regions, ignite-fall-2021
 ms.devlang: 
 ms.topic: conceptual
-ms.date: 03/07/2022
+ms.date: 04/26/2022
 ---
 # What's new in Azure SQL Database?
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -40,7 +40,6 @@ The following table lists the features of Azure SQL Database that are currently
 | [SQL Analytics](/azure/azure-monitor/insights/azure-sql)|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. Azure SQL Analytics collects and visualizes key performance metrics with built-in intelligence for performance troubleshooting.|
 | [SQL Insights (preview)](/azure/azure-monitor/insights/sql-insights-overview) | SQL Insights (preview) is a comprehensive solution for monitoring any product in the Azure SQL family. SQL Insights (preview) uses dynamic management views to expose the data you need to monitor health, diagnose problems, and tune performance.|
 | [Zone redundant configuration for Hyperscale databases](high-availability-sla.md#hyperscale-service-tier-zone-redundant-availability-preview) | The zone redundant configuration feature utilizes [Azure Availability Zones](/azure/availability-zones/az-overview#availability-zones) to replicate databases across multiple physical locations within an Azure region. By selecting [zone redundancy](high-availability-sla.md#hyperscale-service-tier-zone-redundant-availability-preview), you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic.|
-|||
 
 ## General availability (GA)
 
@@ -56,7 +55,6 @@ The following table lists the features of Azure SQL Database that have transitio
 | [Audit management operations](../database/auditing-overview.md#auditing-of-microsoft-support-operations) |  March 2021 | Azure SQL audit capabilities enable you to audit operations done by Microsoft support engineers when they need to access your SQL assets during a support request, enabling more transparency in your workforce. | 
 
 
-
 ## Documentation changes
 
 Learn about significant changes to the Azure SQL Database documentation.

azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml

@@ -43,7 +43,7 @@ sections:
       - question: |
           Who should use the Hyperscale service tier?
         answer: |
-          The Hyperscale service tier is intended for customers who have large on-premises SQL Server databases and want to modernize their applications by moving to the cloud, or for customers who are already using Azure SQL Database and want to significantly expand the potential for database growth. Hyperscale is also intended for customers who seek both high performance and high scalability. With Hyperscale, you get:
+          The Hyperscale service tier is for all customers who require higher performance, fast backups, and/or storage and compute scalability, including both customers who are moving to the cloud to modernize their applications and customers who are already using other service tiers in Azure SQL Database. With Hyperscale, you get:
           
           - Database size up to 100 TB
           - Fast database backups regardless of database size (backups are based on storage snapshots)
@@ -77,9 +77,10 @@ sections:
             With  Hyperscale, you can scale up the primary compute size in terms of resources like CPU and memory, and then scale down, in constant time. Because the storage is shared, scaling up and scaling down is not a size of data operation.  
           - **Scaling In/Out**
           
-            With Hyperscale, you also get the ability to provision one or more additional compute replicas that you can use to serve your read requests. This means that you can use these additional compute replicas as read-only replicas to offload your read workload from the primary compute. In addition to read-only, these replicas also serve as hot-standbys in case of a failover from the primary.
-          
-            Provisioning of each of these additional compute replicas can be done in constant time and is an online operation. You can connect to these additional read-only compute replicas by setting the `ApplicationIntent` argument on your connection string to `ReadOnly`. Any connections  with the `ReadOnly` application intent are automatically routed to one of the additional read-only compute replicas.
+            With Hyperscale, you get the flexibility to include 3 types of secondary replicas to cater read scale-out, high availability, and geo-replication requirements. 
+            - Up to 4 [high-availability replicas](service-tier-hyperscale-replicas.md#high-availability-replica) having same compute size as primary to offload read workloads from the primary compute and to also serve as a hot-standby in case of an unexpected failure of the primary.
+            - Up to 30 [named replicas](service-tier-hyperscale-replicas.md#named-replica-in-preview) having same or different compute size than primary to cater massive read scale-out scenarios.  
+            - A [Geo-replica](service-tier-hyperscale-replicas.md#geo-replica-in-preview) in the same or different Azure region to offload that can enable regional resiliency.
           
   - name: Deep dive questions
     questions:
@@ -158,7 +159,7 @@ sections:
           The transaction log on hyperscale is practically infinite, with the restriction that a single transaction cannot generate more than 1TB of log. Additionally, if using [Change Data Capture](/sql/relational-databases/track-changes/about-change-data-capture-sql-server), at most 1 TB of log can be generated since the start of the  oldest active transaction. It is recommended to avoid unnecessarily large transactions to stay below this limit. Other than the restrictions stated, you do not need to worry about running out of log space on a system that has a high log throughput. However, log generation rate might be throttled for continuous aggressively writing workloads. The peak sustained log generation rate is 100 MB/s.
 
       - question: |
-          Does my `tempdb` scale as my database grows?
+          Does my tempdb scale as my database grows?
         answer: |
           Your `tempdb` database is located on local SSD storage and is sized proportionally to the compute size that you provision. Your `tempdb` is optimized to provide maximum performance benefits. `tempdb` size is not configurable and is managed for you. To determine maximum `tempdb` size for your database, see [Hyperscale storage and compute sizes](resource-limits-vcore-single-databases.md#hyperscale---provisioned-compute---gen5).
 
@@ -407,7 +408,7 @@ sections:
           End-user. Not automatic.  
 
       - question: |
-          Does the size of my `tempdb` database and RBPEX cache also grow as the compute is scaled up?
+          Does the size of my tempdb database and RBPEX cache also grow as the compute is scaled up?
         answer: |
           Yes. The `tempdb` database and [RBPEX cache](service-tier-hyperscale.md#distributed-functions-architecture) size on compute nodes will scale up automatically as the number of cores is increased. For details, see [Hyperscale storage and compute sizes](resource-limits-vcore-single-databases.md#hyperscale---provisioned-compute---gen5).
           
@@ -454,7 +455,7 @@ sections:
           No. HA replicas are used as high availability failover targets, so they need to have the same configuration as the primary to provide expected performance after failover. [Named replicas](service-tier-hyperscale-replicas.md#named-replica-in-preview) provide the ability to scale each replica independently.
 
       - question: |
-          Do I get different `tempdb` sizing for my primary compute and my HA replicas?
+          Do I get different tempdb sizing for my primary compute and my HA replicas?
         answer: |
           No. Your `tempdb` database is configured based on the provisioned compute size, your HA replicas are the same size, including `tempdb`, as the primary compute. On [named replicas](service-tier-hyperscale-replicas.md#named-replica-in-preview), `tempdb` is sized according to the compute size of the replica, thus it can be smaller or larger than `tempdb` on the primary.
 

azure-sql/database/service-tier-hyperscale.md

@@ -10,7 +10,7 @@ ms.topic: conceptual
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: kendralittle, mathoma
-ms.date: 03/02/2022
+ms.date: 04/26/2022
 ---
 
 # Hyperscale service tier
@@ -124,7 +124,6 @@ You can create and manage Hyperscale databases using the [Azure portal](https://
 |**Create a Hyperscale database**| Hyperscale databases are available only using the [vCore-based purchasing model](service-tiers-vcore.md). | Find examples to create a Hyperscale database in [Quickstart: Create a Hyperscale database in Azure SQL Database](hyperscale-database-create-quickstart.md). |
 | **Upgrade an existing database to Hyperscale** | Migrating an existing database in Azure SQL Database to the Hyperscale tier is a size of data operation. | Learn [how to migrate an existing database to Hyperscale](manage-hyperscale-database.md#migrate-an-existing-database-to-hyperscale).|
 | **Reverse migrate a Hyperscale database to the General Purpose service tier (preview)** | If you previously migrated an existing Azure SQL Database to the Hyperscale service tier, you can reverse migrate the database to the General Purpose service tier within 45 days of the original migration to Hyperscale.<BR/><BR/>If you wish to migrate the database to another service tier, such as Business Critical, first reverse migrate to the General Purpose service tier, then change the service tier. | Learn [how to reverse migrate from Hyperscale](manage-hyperscale-database.md#reverse-migrate-from-hyperscale), including the [limitations for reverse migration](manage-hyperscale-database.md#limitations-for-reverse-migration).|
-| | | |
 
 ## Database high availability in Hyperscale
 

azure-sql/docfx.json

@@ -64,7 +64,12 @@
       "brand": "azure",
       "toc_preview": true,
       "titleSuffix": "Azure SQL",
-      "recommendations": true
+      "recommendations": true,
+      "_op_documentIdPathDepotMapping": {
+        "./": {
+           "depot_name": "Azure.azure-documents"
+        }
+      }
     },
     "fileMetadata": {
       "breadcrumb_path": {

azure-sql/index.yml

@@ -1,10 +1,10 @@
 ### YamlMime:Landing
 
-title: Azure SQL documentation - Azure Staged
+title: Azure SQL documentation
 summary: "Find documentation about the Azure SQL family of SQL Server database engine products in the cloud: Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VM."
 
 metadata:
-  title: Azure SQL documentation - Azure Staged
+  title: Azure SQL documentation
   description:  "Azure SQL is a family of SQL Server database engine products in the cloud, from a fully managed database in Azure SQL Database, a fully managed instance in Azure SQL Managed Instance, or SQL Server installed to virtual machine in Azure."
   services: sql-database
   ms.service: sql-db-mi

docs/relational-databases/system-dynamic-management-views/sys-dm-db-index-physical-stats-transact-sql.md

@@ -106,7 +106,7 @@ sys.dm_db_index_physical_stats (
 |avg_record_size_in_bytes|**float**|Average record size in bytes.<br /><br /> For an index, the average record size applies to the current level of the B-tree in the IN_ROW_DATA allocation unit.<br /><br /> For a heap, the average record size in the IN_ROW_DATA allocation unit.<br /><br /> For LOB_DATA or ROW_OVERFLOW_DATA allocation units, the average record size in the complete allocation unit.<br /><br /> NULL when *mode* = LIMITED.|  
 |forwarded_record_count|**bigint**|Number of records in a heap that have forward pointers to another data location. (This state occurs during an update, when there is not enough room to store the new row in the original location.)<br /><br /> NULL for any allocation unit other than the IN_ROW_DATA allocation units for a heap.<br /><br /> NULL for heaps when *mode* = LIMITED.|  
 |compressed_page_count|**bigint**|The number of compressed pages.<br /><br /> For heaps, newly allocated pages are not PAGE compressed. A heap is PAGE compressed under two special conditions: when data is bulk imported or when a heap is rebuilt. Typical DML operations that cause page allocations will not be PAGE compressed. Rebuild a heap when the compressed_page_count value grows larger than the threshold you want.<br /><br /> For tables that have a clustered index, the compressed_page_count value indicates the effectiveness of PAGE compression.|  
-|hobt_id|bigint|For columnstore indexes only, this is the ID for a rowset that tracks internal columnstore data for a partition. The rowsets are stored as data heaps or binary trees. They have the same index ID as the parent columnstore index. For more information, see [sys.internal_partitions &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-internal-partitions-transact-sql.md).<br /><br /> NULL if <br /><br /> **Applies to**: SQL Server 2016 and later, Azure SQL Database, Azure SQL Managed Instance|  
+|hobt_id|bigint|For columnstore indexes only, this is the ID for a rowset that tracks internal columnstore data for a partition. The rowsets are stored as data heaps or B-trees. They have the same index ID as the parent columnstore index. For more information, see [sys.internal_partitions &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-internal-partitions-transact-sql.md).<br /><br /> NULL if <br /><br /> **Applies to**: SQL Server 2016 and later, Azure SQL Database, Azure SQL Managed Instance|  
 |column_store_delete_buffer_state|tinyint| 0 = NOT_APPLICABLE<br /><br /> 1 = OPEN<br /><br /> 2 = DRAINING<br /><br /> 3 = FLUSHING<br /><br /> 4 = RETIRING<br /><br /> 5 = READY<br /><br />**Applies to**: SQL Server 2016 and later, Azure SQL Database, Azure SQL Managed Instance|  
 |column_store_delete_buff_state_desc|| NOT VALID -the parent index is not a columnstore index.<br /><br /> OPEN - deleters and scanners use this.<br /><br /> DRAINING - deleters are draining out but scanners still use it.<br /><br /> FLUSHING - buffer is closed and rows in the buffer are being written to the delete bitmap.<br /><br /> RETIRING - rows in the closed delete buffer have been written to the delete bitmap, but the buffer has not been truncated because scanners are still using it. New scanners don't need to use the retiring buffer because the open buffer is enough.<br /><br /> READY - This delete buffer is ready for use. <br /><br /> **Applies to**: SQL Server 2016 and later, Azure SQL Database, Azure SQL Managed Instance|  
 |version_record_count|**bigint**|This is the count of the row version records being maintained in this index.  These row versions are maintained by the [Accelerated Database Recovery](../../relational-databases/accelerated-database-recovery-concepts.md) feature. <br /><br /> [!INCLUDE[SQL2019](../../includes/applies-to-version/sqlserver2019.md)], [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] |  

docs/reporting-services/release-notes-reporting-services.md

@@ -1,7 +1,7 @@
 ---
 title: "Release notes for Reporting Services 2017 and later | Microsoft Docs"
 description: Learn details about the changes in SQL Server Reporting Services (SSRS), for versions 2017 and later.
-ms.date: 04/05/2022
+ms.date: 04/25/2022
 ms.prod: reporting-services
 ms.prod_service: reporting-services-native
 ms.technology: reporting-services
@@ -111,6 +111,14 @@ Initial release.
 
 ## SQL Server 2017 Reporting Services
 
+## 14.0.600.1860, 2022/04/26 
+*(Product Version: 14.0.600.1860)*
+
+| Fixed issue | Details |
+| :---------- | :------ |
+| Fixed an issue rendering some reports in Edge browser.  |   |
+| Fixed an issue for some locales when working with data from an Essbase datasource.  |   |
+
 ## 14.0.600.1763, 2021/06/28 
 *(Product Version: 14.0.600.1763)*