Merge pull request #19378 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to master to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/database-engine/availability-groups/windows/distributed-availability-groups.md

@@ -130,7 +130,7 @@ Distributed availability groups can help you scale out a read-only farm more tha
 * You can use the primary replica of the second availability group in a distributed availability group to create another distributed availability group, even though the database is not in RECOVERY.
 * You can also use the primary replica of the first availability group to create another distributed availability group.
 
-In other words, a primary replica can participate in two different distributed availability groups. The following figure shows AG 1 and AG 2 both participating in Distributed AG 1, while AG 2 and AG 3 are participating in Distributed AG 2. The primary replica (or forwarder) of AG 2 is both a secondary replica for Distributed AG 1 and a primary replica of Distributed AG 2.
+In other words, a primary replica can participate in different distributed availability groups. The following figure shows AG 1 and AG 2 both participating in Distributed AG 1, while AG 2 and AG 3 are participating in Distributed AG 2. The primary replica (or forwarder) of AG 2 is both a secondary replica for Distributed AG 1 and a primary replica of Distributed AG 2.
 
 ![Scaling out reads with distributed availability groups](./media/distributed-availability-group/dag-05-scaling-out-reads-with-distributed-ags.png)
 
@@ -404,4 +404,4 @@ The below query displays information about the current state of seeding. This is
 
 * [Use the new availability group dialog box (SQL Server Management Studio)](use-the-new-availability-group-dialog-box-sql-server-management-studio.md)
 
-* [Create an availability group with Transact-SQL](create-an-availability-group-transact-sql.md)
+* [Create an availability group with Transact-SQL](create-an-availability-group-transact-sql.md)

docs/relational-databases/errors-events/mssqlserver-605-database-engine-error.md

@@ -50,7 +50,7 @@ If the 605 error is not transient, the problem is severe and must be corrected b
 1.  Identify the tables associated with the allocation units specified in the message by running the following query. Replace `allocation_unit_id` with the allocation units specified in the error message.  
 
     ```sql  
-    USE`database_name`;  
+    USE [database_name];  
 
     GO  
 

docs/relational-databases/resource-governor/create-and-test-a-classifier-user-defined-function.md

@@ -58,11 +58,10 @@ ms.author: wiassaf
     WITH  
     (  
          IMPORTANCE = MEDIUM  
-    );  
-    
+    )
     --- Assign the workload group to the production processing  
     --- resource pool.  
-    USING pProductionProcessing  
+    USING pProductionProcessing;
     GO  
 
     --- Create a resource pool for off-hours processing  

docs/relational-databases/system-views/syssubscriptions-system-view-transact-sql.md

@@ -34,7 +34,7 @@ ms.author: wiassaf
 |**login_name**|**sysname**|The login name used when connecting to the Publisher to add the subscription.|  
 |**subscription_type**|**int**|The type of subscription:<br /><br /> **0** = Push - the distribution agent runs at the Distributor.<br /><br /> **1** = Pull - the distribution agent runs at the Subscriber.|  
 |**distribution_jobid**|**binary(16)**|Identifies the Distribution Agent job used to synchronize the subscription.|  
-|**timestmap**|**timestamp**|The date and time that the subscription was created.|  
+|**timestamp**|**timestamp**|The date and time that the subscription was created.|  
 |**update_mode**|**tinyint**|The update mode:<br /><br /> **0** = Read-only.<br /><br /> **1** = Immediate-updating.|  
 |**loopback_detection**|**bit**|Applies to subscriptions that are part of a bidirectional transactional replication topology. Loopback detection determines whether the Distribution Agent sends transactions originated at the Subscriber back to the Subscriber:<br /><br /> **0** = Sends back.<br /><br /> **1** = Does not send back.|  
 |**queued_reinit**|**bit**|Specifies whether the article is marked for initialization or reinitialization. A value of **1** specifies that the subscribed article is marked for initialization or reinitialization.|  

docs/reporting-services/install-windows/power-bi-report-server-integration-configuration-manager.md

@@ -25,7 +25,10 @@ In addition to an active internet connection so you can browse to the [!INCLUDE[
 
 - The user performing the [!INCLUDE[sspowerbi](../../includes/sspowerbi-md.md)] integration needs to be a member of the Azure AD tenant, a [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] system administrator and a system administrator for the ReportServer catalog database.
 
-- The user performing the [!INCLUDE[sspowerbi](../../includes/sspowerbi-md.md)] integration needs to start the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration Manager either with the account used to install [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)], or the account the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] service is running under
+- The user performing the [!INCLUDE[sspowerbi](../../includes/sspowerbi-md.md)] integration needs to start the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration Manager either with the account used to install [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)], or the account the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] service is running under.
+
+- The server with Reporting Services installed needs to be configured to use TLS 1.2 or newer. For more information, see [Transport Layer Security (TLS) best practices with the .NET Framework](/dotnet/framework/network-programming/tls).
+
 
 - Reports that you want to pin from must use stored credentials. This is not a requirement of the [!INCLUDE[sspowerbi](../../includes/sspowerbi-md.md)] integration itself but of the refresh process for the pinned items.  The action of pinning a report item creates a [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] subscription to manage the refresh schedule of the tiles in [!INCLUDE[sspowerbi](../../includes/sspowerbi-md.md)]. [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] subscriptions require stored credentials. If a report does not use stored credentials, a user can still pin report items but when the associated subscription attempts to refresh the data to [!INCLUDE[sspowerbi](../../includes/sspowerbi-md.md)], you will see an error message similar to the following on the **My Subscriptions** page.
 
@@ -152,4 +155,4 @@ The second time a user pins an item, the steps 1-4 are skipped and instead the A
 [Pin Reporting Services items to Power BI Dashboards](../../reporting-services/pin-reporting-services-items-to-power-bi-dashboards.md)
 [Dashboards in Power BI](https://powerbi.microsoft.com/documentation/powerbi-service-dashboards/)  
 
-More questions? [Try asking the Reporting Services forum](https://go.microsoft.com/fwlink/?LinkId=620231)
+More questions? [Try asking the Reporting Services forum](https://go.microsoft.com/fwlink/?LinkId=620231)

docs/t-sql/queries/from-using-pivot-and-unpivot.md

@@ -89,14 +89,16 @@ The following code displays the same result, pivoted so that the `DaysToManufact
 ```sql
 -- Pivot table with one row and five columns  
 SELECT 'AverageCost' AS Cost_Sorted_By_Production_Days,   
-[0], [1], [2], [3], [4]  
+  [0], [1], [2], [3], [4]  
 FROM  
-(SELECT DaysToManufacture, StandardCost   
-    FROM Production.Product) AS SourceTable  
+(
+  SELECT DaysToManufacture, StandardCost   
+  FROM Production.Product
+) AS SourceTable  
 PIVOT  
 (  
-AVG(StandardCost)  
-FOR DaysToManufacture IN ([0], [1], [2], [3], [4])  
+  AVG(StandardCost)  
+  FOR DaysToManufacture IN ([0], [1], [2], [3], [4])  
 ) AS PivotTable;  
 
 ```