Merge pull request #30436 from MicrosoftDocs/main

4/22/2024 AM Publish

Author: Albertyang0

azure-sql/database/sql-insights-troubleshoot.md

@@ -5,7 +5,7 @@ description: Learn how to troubleshoot SQL Insights (preview) in Azure Monitor.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma
-ms.date: 10/18/2022
+ms.date: 04/22/2024
 ms.service: sql-db-mi
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -194,8 +194,9 @@ During preview of SQL Insights, you may encounter the following known issues.
 
     Using certain special characters in SQL authentication passwords saved in the monitoring VM configuration or in Key Vault may prevent the monitoring VM from connecting to a SQL server or database. This set of characters includes parentheses, square and curly brackets, the dollar sign, forward and back slashes, and dot (`[ { ( ) } ] $ \ / .`).
 * Spaces in the database connection string attributes may be replaced with special characters, leading to database connection failures. For example, if the space in the `User Id` attribute is replaced with a special character, connections will fail with the **Login failed for user ''** error. To resolve, edit the monitoring profile configuration, and delete every special character appearing in place of a space. Some special characters may look indistinguishable from a space, thus you may want to delete every space character, type it again, and save the configuration.
-* Data collection and visualization may not work if the OS computer name of the monitoring VM is different from the monitoring VM name.
+* Data collection and visualization might not work if the OS computer name of the monitoring VM is different from the monitoring VM name.
 * A message "WLI extension on this machine is below the recommended version [...]" may incorrectly appear even when the WLI extension is up to date.
+* Data collection and visualization might not work if the OS computer name of the VM where SQL Server is installed does not match the server name in the SQL Server metadata. For more information, see [Rename a computer that hosts a stand-alone instance of SQL Server](/sql/database-engine/install-windows/rename-a-computer-that-hosts-a-stand-alone-instance-of-sql-server).
 
 ## Best practices
 

docs/relational-databases/system-tables/dbo-sysproxylogin-transact-sql.md

@@ -3,7 +3,7 @@ title: "dbo.sysproxylogin (Transact-SQL)"
 description: dbo.sysproxylogin (Transact-SQL)
 author: VanMSFT
 ms.author: vanto
-ms.date: "06/10/2016"
+ms.date: "04/19/2024"
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -20,19 +20,19 @@ dev_langs:
 # dbo.sysproxylogin (Transact-SQL)
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-  Records which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] logins are associated with each SQL Server Agent proxy account. This table is stored in the **msdb** database.  
+  Shows which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] logins are associated with each SQL Server Agent proxy account. This table is stored in the **msdb** database.  
 
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |**proxy_id**|**int**|ID of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent proxy account. This value corresponds to the **proxy_id** column in the **sysproxies** table.|  
 |**sid**|**varbinary(85)**|Microsoft Windows *security_identifier* for the SQL Server login.|  
-|**principal_id**|**int**|ID of the user or group that has permission to use the proxy account for a specified subsystem step.|  
-|**flags**|**int**|Type of login:<br /><br /> **0** = Windows user or group, and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] login.<br /><br /> **1** = [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] fixed system role<br /><br /> **2** = **msdb** database role|  
+|**flags**|**int**|Type of `login`:<br /><br /> **0** = Windows user or group, and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] login.<br /><br /> **1** = [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] fixed system role<br /><br /> **2** = **msdb** database role|  
 
 ## Remarks  
  Only members of the **sysadmin** fixed server role can access this table.  
 
-## See Also  
- [dbo.sysproxies &#40;Transact-SQL&#41;](../../relational-databases/system-tables/dbo-sysproxies-transact-sql.md)  
+## Related content
+
+[dbo.sysproxies &#40;Transact-SQL&#41;](../../relational-databases/system-tables/dbo-sysproxies-transact-sql.md)  
 
 

docs/relational-databases/tables/manage-retention-of-historical-data-in-system-versioned-temporal-tables.md

@@ -248,7 +248,7 @@ DECLARE @historyTableSchema SYSNAME
 DECLARE @periodColumnName SYSNAME
 
 /*Generate script to discover history table name and end of period column for given temporal table name*/
-EXECUTE usp_executesql
+EXECUTE sp_executesql
 N'SELECT @hst_tbl_nm = t2.name,
       @hst_sch_nm = s2.name,
       @period_col_nm = c.name
@@ -263,7 +263,8 @@ N'@tblName sysname,
     @schName sysname,
     @hst_tbl_nm sysname OUTPUT,
     @hst_sch_nm sysname OUTPUT,
-    @period_col_nm sysname OUTPUT' @tblName = @temporalTableName,
+    @period_col_nm sysname OUTPUT',
+@tblName = @temporalTableName,
 @schName = @temporalTableSchema,
 @hst_tbl_nm = @historyTableName OUTPUT,
 @hst_sch_nm = @historyTableSchema OUTPUT,