Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into release-2019-cu

Author: v-alje

docs/relational-databases/system-catalog-views/sys-servers-transact-sql.md

@@ -53,6 +53,7 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 |**is_nonsql_subscriber**|**bit**|Server is a non-SQL Server replication Subscriber.|  
 |**is_remote_proc_transaction_promotion_enabled**|**bit**|If 1, calling a remote stored procedure starts a distributed transaction and enlists the transaction with MS DTC. For more information, see [sp_serveroption (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-serveroption-transact-sql.md).|  
 |**modify_date**|**datetime**|Date that server information was last changed.|  
+|**is_rda_server**|**bit**|Server is remote data archive enable (stretch-enabled). For more information, see [Enable Stretch Database on the server](https://docs.microsoft.com/sql/sql-server/stretch-database/enable-stretch-database-for-a-database#EnableTSQLServer). Applies to SQL Server 2016 and newer.|
 
 ## Permissions  
  The value in **provider_string** is always NULL unless the caller has the ALTER ANY LINKED SERVER permission.  

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-exec-requests-transact-sql.md

@@ -38,7 +38,7 @@ monikerRange: ">= aps-pdw-2016 || = azure-sqldw-latest || = sqlallproducts-allve
 |group_name|**sysname** |For requests utilizing resources, group_name is the name of the workload group the request is running under.  If the request does not utilize resources, group_name is null.</br>Applies to: Azure SQL Data Warehouse|
 |classifier_name|**sysname**|For requests utilizing resources, The name of the classifier used for assigning resources and importance.||
 |resource_allocation_percentage|**decimal(5,2)**|The percentage amount of resources allocated to the request.</br>Applies to: Azure SQL Data Warehouse|
-|result_cache_hit|**hexadecimal**|Details whether a completed query used result set cache.  </br>Applies to: Azure SQL Data Warehouse| 1 = Result set cache hit </br> 0 = Result set cache miss </br> Negative values = Reasons why result set caching was not used.  See remarks section for details.|
+|result_cache_hit|**decimal**|Details whether a completed query used result set cache.  </br>Applies to: Azure SQL Data Warehouse| 1 = Result set cache hit </br> 0 = Result set cache miss </br> Negative values = Reasons why result set caching was not used.  See remarks section for details.|
 ||||
 
 ## Remarks 

docs/reporting-services/report-design/customize-the-parameters-pane-in-a-report-report-builder.md

@@ -1,7 +1,7 @@
 ---
 title: "Customize the Parameters Pane in a Report (Report Builder) | Microsoft Docs"
 description: Learn how to customize the Parameters pane when creating paginated reports with parameters in Report Builder.
-ms.date: 03/01/2017
+ms.date: 06/15/2020
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: report-design
@@ -59,30 +59,30 @@ ms.author: maggies
 
     -   Right click parameter in the **Report Data** pane, and then click **Delete**.
 
-## Hidden/Internal parameters in runtime
-If you have hidden/internal parameters, the logic on whether it'll be rendered as empty space in runtime is as follows:
+## Hidden/Internal parameters during runtime
+If you have a hidden/internal parameter, the logic of whether it will be rendered as empty space during runtime is as follows:
 
-   - If any row or column is full of hidden/internal parameters or empty cell, then it won't be rendered in runtime;
-   - Otherwise, both hidden/internal parameters and empty cell will be rendered as empty space;
+   - If any row or column contains only hidden/internal parameters or empty cells, then the entire row or column won't be rendered during runtime
+   - Otherwise, the hidden/internal parameter or empty cell will be rendered as empty space
 
-For example, `ReportParameter1` is hidden while rests are visible:
+For example, `ReportParameter1` is hidden while the rest of the parameters are visible:
 
 ![Hidden Parameter Example 1](../../reporting-services/report-design/media/ssrs-hidden-parameter-rb-1.png "One hidden parameter in layout grid")
 
-This will result in an empty space in runtime because there are visible parameters in first column or first row:
+This will result as an empty space during runtime because there are visible parameters in first column or first row:
 
 ![Hidden Parameter Example 1 - runtime](../../reporting-services/report-design/media/ssrs-hidden-parameter-server-1.png "One hidden parameter in layout grid result in empty space in runtime")
 
-Now if we change `ReportParameter3` to hidden as well:
+Using the same example, if you also set `ReportParameter3` as hidden:
 
 ![Hidden Parameter Example 2](../../reporting-services/report-design/media/ssrs-hidden-parameter-rb-2.png "Two hidden parameter in same column")
 
-Then the first column is omitted because the whole column is empty:
+Then the first column is not rendered during runtime because the entire column is considered empty:
 
 ![Hidden Parameter Example 2 - runtime](../../reporting-services/report-design/media/ssrs-hidden-parameter-server-2.png "Two hidden parameter in same column in runtime")
 
 ## Default layout
-For those reports that were authored before SSRS 2016 version, a default layout grid of 2 columns and N rows will be used in runtime. To change the layout, simply open the report in latest Report Builder and save back, then a customized layout info will be saved to .rdl file as well.
+For reports that were authored before SQL Server Reporting Services 2016, a default parameter layout grid of 2 columns and N rows will be used during runtime. To change the default layout, open the report in Microsoft Report Builder and save the report. After saving the report, the customized parameter layout information will be saved to the .rdl file.
 
 
 ## See also