Merge pull request #33173 from MicrosoftDocs/main

2/14/2025 AM Publish

Author: Albertyang0

azure-sql/database/automatic-tuning-overview.md

@@ -1,6 +1,6 @@
 ---
 title: Automatic Tuning Overview
-titleSuffix: Azure SQL Database & Azure SQL Managed Instance
+titleSuffix: Azure SQL & SQL database in Fabric
 description: Automatic tuning analyzes SQL query and automatically adapts to user workload.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
@@ -14,7 +14,7 @@ ms.custom:
   - ignite-2024
 monikerRange: "=azuresql || =azuresql-db || =azuresql-mi || =fabric"
 ---
-# Automatic tuning in Azure SQL Database and Azure SQL Managed Instance
+# Automatic database tuning
 
 [!INCLUDE[appliesto-sqldb-sqlmi-fabricsqldb](../includes/appliesto-sqldb-sqlmi-fabricsqldb.md)]
 

azure-sql/database/media/monitoring-with-dmvs/sql_db_resource_utilization.png renamed to azure-sql/database/media/monitoring-with-dmvs/sql-db-resource-utilization.png

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot common connection issues
-titleSuffix: Azure SQL Database & Azure SQL Managed Instance
+titleSuffix: Azure SQL & SQL database in Fabric
 description: Provides steps to troubleshoot connection issues and resolve other connectivity issues in Azure SQL Database, Fabric SQL database, or Azure SQL Managed Instance.
 author: suresh-kandoth
 ms.author: sureshka

azure-sql/database/media/secure-database-tutorial/audit-records.png

@@ -1,10 +1,10 @@
 ---
-title: "SQL Server Browser service"
+title: "SQL Server Browser Service"
 description: Learn how to use SQL Server Browser, a service that listens for requests for SQL Server resources and provides information about installed SQL Server instances.
 author: markingmyname
 ms.author: maghan
-ms.reviewer: vanto
-ms.date: 09/11/2024
+ms.reviewer: vanto, randolphwest
+ms.date: 02/13/2025
 ms.service: sql
 ms.subservice: tools-other
 ms.topic: conceptual
@@ -56,7 +56,7 @@ Upon startup, the SQL Server Browser starts and claims UDP port 1434. SQL Server
 
 When SQL Server clients request SQL Server resources, the client network library sends a UDP message to the server using port 1434. SQL Server Browser responds with the TCP/IP port or named pipe of the requested instance. The network library on the client application then completes the connection by sending a request to the server using the port or named pipe of the desired instance.
 
-Learn how to start and stop the SQL Server Browser service in the article [Start, stop, pause, resume, restart SQL Server services](../../database-engine/configure-windows/start-stop-pause-resume-restart-sql-server-services.md).
+For more information on starting and stopping the SQL Server Browser service, see [Start, stop, pause, resume, and restart SQL Server services](../../database-engine/configure-windows/start-stop-pause-resume-restart-sql-server-services.md).
 
 ## Use SQL Server Browser
 
@@ -65,33 +65,38 @@ If the SQL Server Browser service isn't running, you can still connect to the SQ
 However, if the SQL Server Browser service isn't running, the following connections don't work:
 
 - Any component that tries to connect to a named instance without fully specifying all the parameters (such as the TCP/IP port or named pipe).
-- Any component that generates or passes server\instance information that other components could later use to reconnect.
+
+- Any component that generates or passes `<server>\<instance>` information that other components could later use to reconnect.
+
 - Connecting to a named instance without providing the port number or pipe.
-- [DAC](../../database-engine/configure-windows/diagnostic-connection-for-database-administrators.md) to a named instance or the default instance if not using TCP/IP port 1433.
+
+- [Diagnostic connection for database administrators](../../database-engine/configure-windows/diagnostic-connection-for-database-administrators.md) to a named instance or the default instance if not using TCP/IP port 1433.
+
 - The Online Analytical Processing (OLAP) redirector service.
-- Enumerating servers in [SQL Server Management Studio](../../ssms/menu-help/about-sql-server-management-studio.md) or [Azure Data Studio](/azure-data-studio/download-azure-data-studio).
 
-Suppose you're using SQL Server in a client-server scenario (for example, when your application is accessing SQL Server across a network). If you stop or disable the SQL Server Browser service, you must assign a specific port number to each instance and write your client application code to use that port number. This approach has the following problems:
+- Enumerating servers in [SQL Server Management Studio](../../ssms/menu-help/about-sql-server-management-studio.md).
+
+Suppose you're using SQL Server in a client-server scenario (for example, when your application is accessing SQL Server across a network). If you stop or disable the SQL Server Browser service, you must assign a specific port number to each instance and configure your client application code to use that port number. This approach has the following problems:
 
 - You must update and maintain client application code to ensure it's connecting to the proper port.
-- The port you choose for each instance might be used by another service or application on the server, causing the instance of SQL Server to be unavailable.
+
+- The port you choose for each instance could be used by another service or application on the server, causing the instance of SQL Server to be unavailable.
 
 ## Clusters and SQL Server Browser
 
 SQL Server Browser isn't a clustered resource and doesn't support failover from one cluster node to the other. Therefore, if there's a cluster, SQL Server Browser should be installed and turned on for each cluster node. On clusters, the SQL Server Browser listens on `IP_ANY`.
 
-> [!NOTE]  
-> When listening on IP_ANY, when you enable listening on specific IPs, the user must configure the same TCP port on each IP because SQL Server Browser returns the first IP/port pair it encounters.
+When the SQL Server Browser listens on `IP_ANY` and you enable listening on specific IP addresses, you must configure the same TCP/IP port on each IP address, because SQL Server Browser returns the first IP address and port pair it encounters.
 
 ## Install, uninstall, and run from the command line
 
-By default, the SQL Server Browser program is installed at *C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe*.
+By default, the SQL Server Browser program is installed at `<drive>:\Program Files (x86)\Microsoft SQL Server\<nn>\Shared\sqlbrowser.exe`.
 
 The SQL Server Browser service is uninstalled when the last instance of SQL Server is removed.
 
-SQL Server Browser can be started from the command prompt for troubleshooting by using the **-c** switch:
+SQL Server Browser can be started from the command prompt for troubleshooting by using the `-c` switch:
 
-```dos
+```cmd
 <drive>\<path>\sqlbrowser.exe -c
 ```
 
@@ -102,9 +107,12 @@ The SQL Server Browser Service is crucial in facilitating network communication
 Security measures for SQL Server Browser Service include:
 
 - Configuring firewalls to allow its traffic.
+
 - Restricting access to trusted IP addresses.
+
 - Regularly applying updates to patch vulnerabilities.
-- Additionally, it's essential to implement strong authentication and authorization policies to prevent unauthorized access and maintain the integrity of your SQL Server environment.
+
+- Additionally, you must implement strong authentication and authorization policies to prevent unauthorized access and maintain the integrity of your SQL Server environment.
 
 ### Account privileges
 
@@ -124,8 +132,8 @@ The minimum user rights for SQL Server Browser are:
 Setup configures SQL Server Browser to use the account selected for services during setup. Other possible accounts include:
 
 - Any **domain\local** account.
-- The **local service** account.
-- The **local system** account (not recommended as it has unnecessary privileges).
+- The **Local Service** account.
+- The **Local System** account (not recommended as it has unnecessary privileges).
 
 ### Hide SQL Server
 

azure-sql/database/monitoring-with-dmvs.md

@@ -1,9 +1,10 @@
 ---
 title: "Viewing the SQL Server Error Log"
-description: Get help detecting problems in SQL Server by viewing the current error log, or backups of previous logs, to check whether processes have finished successfully.
+description: Get help detecting problems in SQL Server by viewing the current error log, or backups of previous logs, to check whether processes finished successfully.
 author: markingmyname
 ms.author: maghan
-ms.date: "03/14/2017"
+ms.reviewer: randolphwest
+ms.date: 02/13/2025
 ms.service: sql
 ms.subservice: tools-other
 ms.topic: conceptual
@@ -16,14 +17,31 @@ helpviewer_keywords:
   - "logs [SQL Server], SQL Server error logs"
 monikerRange: ">=sql-server-2016"
 ---
-# Viewing the SQL Server Error Log
-[!INCLUDE [SQL Server Windows Only](../../includes/applies-to-version/sql-windows-only.md)]
-  View the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error log to ensure that processes have completed successfully (for example, backup and restore operations, batch commands, or other scripts and processes). This can be helpful to detect any current or potential problem areas, including automatic recovery messages (particularly if an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] has been stopped and restarted), kernel messages, or other server-level error messages.  
-  
- View the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error log by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or any text editor. For more information about how to view the error log, see [Open Log File Viewer](../../relational-databases/logs/open-log-file-viewer.md). By default, the error log is located at `Program Files\Microsoft SQL Server\MSSQL.`*n*`\MSSQL\LOG\ERRORLOG` and `ERRORLOG.`*n* files.  
-  
- A new error log is created each time an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is started, although the [sp_cycle_errorlog](../../relational-databases/system-stored-procedures/sp-cycle-errorlog-transact-sql.md) system stored procedure can be used to cycle the error log files without having to restart the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Typically, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] retains backups of the previous six logs and gives the most recent log backup the extension .1, the second most recent the extension .2, and so on. The current error log has no extension.  
-  
- Be aware that you can also view the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error log on instances of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that are offline or cannot start. For more information, see [View Offline Log Files](../../relational-databases/logs/view-offline-log-files.md).  
-  
-  
+# View the SQL Server error log
+
+
+
+[!INCLUDE [SQL Server Windows Only](../../includes/applies-to-version/sqlserver.md)]
+
+View the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] error log to ensure that processes complete successfully (for example, backup and restore operations, batch commands, or other scripts and processes). This procedure can be helpful to detect any current or potential problem areas, including automatic recovery messages (particularly if an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] stopped and restarted), kernel messages, or other server-level error messages.
+
+## How to view the error log
+
+You can view the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] error log with [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or any text editor. For more information about how to view the error log, see [Open Log File Viewer](../../relational-databases/logs/open-log-file-viewer.md).
+
+- On Windows, the default location for the error log is `<drive>:\Program Files\Microsoft SQL Server\MSSQL.<n>\MSSQL\LOG\ERRORLOG`.
+
+- On Linux, the default location for the error log is `/var/opt/mssql/log`.
+
+> [!NOTE]  
+> The files are called `ERRORLOG.<n>`, where `<n>` is an integer. The current error log has no extension.
+
+A new error log is created each time an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is started, although the [sp_cycle_errorlog](../../relational-databases/system-stored-procedures/sp-cycle-errorlog-transact-sql.md) system stored procedure can be used to cycle the error log files without having to restart the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Typically, [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] retains backups of the previous six logs, and gives the most recent log backup the extension `.1`, the second most recent the extension `.2`, and so on. The current error log has no extension.
+
+You can also view the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] error log on instances of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that are offline or can't start. For more information, see [View Offline Log Files](../../relational-databases/logs/view-offline-log-files.md).
+
+## Related content
+
+- [Open Log File Viewer](../../relational-databases/logs/open-log-file-viewer.md)
+- [sp_cycle_errorlog (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-cycle-errorlog-transact-sql.md)
+- [View Offline Log Files](../../relational-databases/logs/view-offline-log-files.md)