Merge pull request #29046 from MicrosoftDocs/main

11/13 sync with the main branch

Author: huypub

docs/ssms/download-sql-server-management-studio-ssms.md

@@ -4,7 +4,7 @@ description: Download the latest version of SQL Server Management Studio (SSMS).
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan
-ms.date: 08/10/2023
+ms.date: 11/13/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: conceptual
@@ -35,27 +35,27 @@ For customers needing a cross-platform companion to SSMS for managing SQL and ot
 
 ## Download SSMS
 
-:::image type="icon" source="../includes/media/download.svg" border="false":::**[Free Download for SQL Server Management Studio (SSMS) 19.1](https://aka.ms/ssmsfullsetup)**
+:::image type="icon" source="../includes/media/download.svg" border="false":::**[Free Download for SQL Server Management Studio (SSMS) 19.2](https://aka.ms/ssmsfullsetup)**
 
-SSMS 19.1 is the latest general availability (GA) version. If you have a *preview* version of SSMS 19 installed, uninstall it before installing SSMS 19.1.  If you have SSMS 19.x installed, installing SSMS 19.1 upgrades it to 19.1.
+SSMS 19.2 is the latest general availability (GA) version. If you have a *preview* version of SSMS 19 installed, uninstall it before installing SSMS 19.2.  If you have SSMS 19.x installed, installing SSMS 19.2 upgrades it to 19.2.
 
-- Release number: 19.1
-- Build number: 19.1.56.0
-- Release date: May 24, 2023
+- Release number: 19.2
+- Build number: 19.2.56.2
+- Release date: November 13, 2023
 
 By using SQL Server Management Studio, you agree to its [license terms](/Legal/sql/sql-server-management-studio-license-terms) and [privacy statement](https://privacy.microsoft.com/privacystatement). If you have comments or suggestions or want to report issues, the best way to contact the SSMS team is at [SQL Server user feedback](https://aka.ms/sqlfeedback).
 
-The SSMS 19.x installation doesn't upgrade or replace SSMS versions 18.x or earlier. SSMS 19.x installs alongside previous versions, so both versions are available. However, if you have an earlier *preview* version of SSMS 19 installed, uninstall it before installing SSMS 19.1. You can see if you have a preview version by going to the **Help > About** window.
+The SSMS 19.x installation doesn't upgrade or replace SSMS versions 18.x or earlier. SSMS 19.x installs alongside previous versions, so both versions are available. However, if you have an earlier *preview* version of SSMS 19 installed, uninstall it before installing SSMS 19.2. You can see if you have a preview version by going to the **Help > About** window.
 
-If a computer contains side-by-side installations of SSMS, verify you start the correct version for your specific needs. The latest version is labeled **Microsoft SQL Server Management Studio v19.1**.
+If a computer contains side-by-side installations of SSMS, verify you start the correct version for your specific needs. The latest version is labeled **Microsoft SQL Server Management Studio v19.2**.
 
 [!INCLUDE [ssms-ads-install](../includes/ssms-azure-data-studio-install.md)]
 
 ## Available languages
 
 This release of SSMS can be installed in the following languages:
 
-SQL Server Management Studio 19.1:  
+SQL Server Management Studio 19.2:  
 [Chinese (Simplified)](https://aka.ms/ssmsfullsetup?clcid=0x804) | [Chinese (Traditional)](https://aka.ms/ssmsfullsetup?clcid=0x404) | [English (United States)](https://aka.ms/ssmsfullsetup?clcid=0x409) | [French](https://aka.ms/ssmsfullsetup?clcid=0x40c) | [German](https://aka.ms/ssmsfullsetup?clcid=0x407) | [Italian](https://aka.ms/ssmsfullsetup?clcid=0x410) | [Japanese](https://aka.ms/ssmsfullsetup?clcid=0x411) | [Korean](https://aka.ms/ssmsfullsetup?clcid=0x412) | [Portuguese (Brazil)](https://aka.ms/ssmsfullsetup?clcid=0x416) | [Russian](https://aka.ms/ssmsfullsetup?clcid=0x419) | [Spanish](https://aka.ms/ssmsfullsetup?clcid=0x40a)
 
 > [!TIP]  

docs/ssms/menu-help/options-output-window-page.md

@@ -4,7 +4,7 @@ description: "Output Window in SQL Server Management Studio"
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan
-ms.date: 1/5/2023
+ms.date: 11/13/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
@@ -26,16 +26,15 @@ Use this page to set the default behavior of the output window.
 
 The Output Window can be opened from the View menu. To access the settings, on the **Tools** menu, select **Options**, and expand the **Output Window** folder or use the key combination Ctrl+Alt+O.
 
-There are four logging channels available to provide more information when using SQL Server Management Studio.
+There are multiple logging channels available to provide more information when using SQL Server Management Studio.
 
 The following table gives an overview of the types of messages associated with each output channel.
 
 | Channel | Definition |
 | ------- | ---------- |
-| **Activity Monitor** | This channel starts when [Activity Monitor](../../relational-databases/performance-monitor/activity-monitor.md) opens for a server. This stream contains events showing part of the query text and timestamp of each query, error messages, and notifications of the monitor being paused due to connectivity problems. If Activity Monitor seems to be idle or otherwise failing to update, check this output channel for more information. |
-| **Azure Activity Directory Interactive authentication** | For cases where Azure Active Directory authentication is used, this channel will output information specific to the authentication process. |
-| **Object Explorer** | This channel outputs the query text and elapsed times of SQL queries needed to expand nodes in Object Explorer. Each query logs a Begin Query and an End Query event. Each event has a timestamp and the URN associated with the entity being queried. The URN refers to the underlying SQL Management Object and consists of an XPath-style hierarchy. For example, the URN for a table named "Table1" in database "Db" on server "MyServer" would be "Server[@Name='MyServer']/Database[@Name='Db']/Table[/@Name='Table1']". Expanding one node in Object Explorer can require multiple such queries with different parameters. The End Query event will contain the elapsed time of the query along with the T-SQL text. You may find this query data useful for server performance analysis in cases where Object Explorer seems unusually slow to expand a particular node. Note: only some nodes in Object Explorer provide this query detail when expanding. Enabled by default. |
-| **SQL Client** | This channel displays information from the Microsoft.Data.SqlClient data provider. This option requires a restart of SSMS for output to appear. |
+| **Object Explorer** | This channel outputs the query text and elapsed times of SQL queries needed to expand nodes in Object Explorer. Each query logs a Begin Query and an End Query event. Each event has a timestamp and the URN associated with the entity being queried. The URN refers to the underlying SQL Management Object and consists of an XPath-style hierarchy. For example, the URN for a table named "Table1" in database "Db" on server "MyServer" would be "Server[@Name='MyServer']/Database[@Name='Db']/Table[/@Name='Table1']". Expanding one node in Object Explorer can require multiple such queries with different parameters. The End Query event contains the elapsed time of the query along with the T-SQL text. This query data is useful for server performance analysis in cases where Object Explorer seems unusually slow to expand a particular node. Note: only some nodes in Object Explorer provide this query detail when expanding. Enabled by default. |
 | **Telemetry** | Telemetry is the stream of anonymous feature usage data collected by Microsoft. These events could be useful for your tracking of SSMS usage. It can help you identify what Object Explorer nodes you expand and what commands run during your SSMS session while the Output window is open. Enabled by default. |
-
-
+| **SQL Client** | This channel displays information from the Microsoft.Data.SqlClient data provider. This option requires a restart of SSMS for output to appear. |
+| **Microsoft Entra Interactive authentication** | For cases where Microsoft Entra authentication is used, this channel outputs information specific to the authentication process. |
+| **Azure REST API** | This channel starts after authentication with Microsoft Entra credentials occurs.  This channel outputs information specific to Azure REST API calls when Azure-connected features are used and more troubleshooting information is needed. |
+| **Activity Monitor** | This channel starts when [Activity Monitor](../../relational-databases/performance-monitor/activity-monitor.md) opens for a server. This stream contains events showing part of the query text and timestamp of each query, error messages, and notifications of the monitor being paused due to connectivity problems. If Activity Monitor is idle or otherwise failing to update, check this output channel for more information. |