Merge pull request #8805 from sevend2/SQLUpdate425

sevend2 · web-flow · commit cf0da0776a34 · 2025-05-06T13:46:05.000+08:00
AB#5606: updates as tr comments
diff --git a/support/sql/database-engine/availability-groups/listener-connection-times-out.md b/support/sql/database-engine/availability-groups/listener-connection-times-out.md
@@ -1,7 +1,7 @@
 ---
 title: Listener connection times out
 description: This article provides resolutions for the timeout error that occurs when you connect to a SQL Server Always On availability group listener in a multi-subnet environment.
-ms.date: 08/04/2020
+ms.date: 05/06/2025
 ms.custom: sap:Always On Availability Groups (AG)
 ms.reviewer: ramakoni
 ---
@@ -10,19 +10,19 @@ ms.reviewer: ramakoni
 
 This article helps you resolve the problem that occurs when you connect to a SQL Server Always On availability group listener in a multi-subnet environment.
 
-_Original product version:_ &nbsp; SQL Server 2012 Developer, SQL Server 2012 Enterprise, SQL Server 2012 Express, SQL Server 2012 Standard, SQL Server 2012 Web, SQL Server 2012 Enterprise Core  
+_Original product version:_ &nbsp; SQL Server 2012 and later versions  
 _Original KB number:_ &nbsp; 2792139
 
 ## Symptoms
 
-After you configure the availability group listener for an Always On Availability Group in Microsoft SQL Server 2012, you may be unable to ping the listener or connect to it from an application.
+After you configure the availability group listener for an Always On Availability Group in Microsoft SQL Server, you might be unable to ping the listener or connect to it from an application.
 
-For example, when you try to connect to a listener of SQL Server by using `SQLCMD`, the connection times out. Additionally, you receive an error message that resembles the following:
+For example, when you try to connect to a listener of SQL Server by using `SQLCMD`, the connection times out. Additionally, you receive an error message that resembles the following one:
 
 > Sqlcmd: Error: Microsoft SQL Native Client: Login timeout expired.
 
 > [!NOTE]
-> These symptoms are usually intermittent, or related to failover of the availability group resource.
+> These symptoms are intermittent, or related to failover of the availability group resource.
 
 The following screenshot shows an example of what occurs when you try to ping the listener for the availability of `aglisten`. The screenshot also shows a successful connection to SQL Server by using the `SQLCMD` command when you include the multi-subnet failover parameter `-M`.
 
@@ -33,20 +33,20 @@ The following screenshot shows an example of what occurs when you try to ping th
 
 ## Cause
 
-This issue occurs because your application either uses a legacy data provider that does not support the new `MultiSubnetFailover` parameter, or isn't configured to use this parameter.
+This issue occurs because your application either uses a legacy data provider that doesn't support the new `MultiSubnetFailover` parameter, or isn't configured to use this parameter.
 
-This parameter is supported in newer versions of the SQLClient driver that is included with the .NET Framework 4 and with later versions of the .NET Framework, and is back ported to the .NET Framework 3.5.
+This parameter is supported in newer versions of the SQLClient driver that is included with the .NET Framework 4 and later versions of the .NET Framework, and is back ported to the .NET Framework 3.5.
 
 > [!NOTE]
-> The `PING` command is a simple connectivity testing tool that does not support the new parameter.
+> The `PING` command is a simple connectivity testing tool that doesn't support the new parameter.
 
 ## Resolution
 
 You can use one of the following resolutions as applicable to your case:
 
 - To resolve this situation when the data providers support the `MultiSubNetFailover` parameter, add the `MultiSubNetFailover` parameter to your connection string, and set it to **true**.
 
-- To resolve this situation when your legacy clients cannot use the `MultiSubnetFailover` property, you can change the listener's `RegisterAllProvidersIP` value to **0**. To do this, run the following command from the Windows PowerShell command-line interface:
+- To resolve this situation when your legacy clients can't use the `MultiSubnetFailover` property, you can change the listener's `RegisterAllProvidersIP` value to **0** by running the following command from the Windows PowerShell command-line interface:
 
     ```powershell
     Import-Module FailoverClusters
@@ -56,22 +56,22 @@ You can use one of the following resolutions as applicable to your case:
     :::image type="content" source="media/listener-connection-times-out/change-listener-registeraiiprovidersip.png" alt-text="Screenshot shows the output of an example of the command in Windows PowerShell.":::
 
 > [!NOTE]
-> After you set the `RegisterAllProvidersIP` value to **0**, the current online IP address must be un-registered from the DNS server and the offline IP address must be registered to the DNS server when a failover occurs. This may cause a connection delay for the next failover.
+> After you set the `RegisterAllProvidersIP` value to **0**, the current online IP address must be unregistered from the DNS server and the offline IP address must be registered to the DNS server when a failover occurs. This might cause a connection delay for the next failover.
 
 ## More information
 
-When you try to connect to a listener that is defined on more than one subnet, the operation may fail if the client driver tries to connect by using one of the listener's offline IP addresses.
+When you try to connect to a listener that is defined on more than one subnet, the operation might fail if the client driver tries to connect by using one of the listener's offline IP addresses.
 
 When a listener is created, an IP address is designated for each unique subnet that an availability group replica is hosted in. For example, if a listener is created for an availability group that has replicas that exist in two subnets, two IP addresses are defined in the listener. One address is used by an application that can connect to an instance of SQL Server in subnet 1, and the other address is used when an application connects to an instance of SQL Server in subnet 2.
 
-Behind the scenes, the listener creates a Windows cluster Client Access Point resource. One of its properties is `RegisterAllProvidersIP`. When a listener is created, this is set to **1**, and all the listener's IP addresses are registered in DNS server. This configuration provides reduced reconnection time for clients.
+Behind the scenes, the listener creates a Windows cluster Client Access Point resource. One of its properties is `RegisterAllProvidersIP`. When a listener is created, this property is set to **1**, and all the listener's IP addresses are registered in DNS server. This configuration provides reduced reconnection time for clients.
 
-Because the DNS record contains all the IP addresses, a client that tries to connect to the listener must know how to handle this situation. The `MultiSubnetFailover` parameter enables the client driver to try connections in parallel to all the listener's IP addresses. Without the `MultiSubnetFailover` parameter, the client driver will try to connect sequentially to all IP addresses for the listener. Sequential connections may cause a long logon time or logon time-outs.
+Because the DNS record contains all the IP addresses, a client that tries to connect to the listener must know how to handle this situation. The `MultiSubnetFailover` parameter enables the client driver to try connections in parallel to all the listener's IP addresses. Without the `MultiSubnetFailover` parameter, the client driver will try to connect sequentially to all IP addresses for the listener. Sequential connections might cause a long logon time or logon time-outs.
 
 > [!NOTE]
 > The problem that is mentioned in this article also affects SharePoint environments that are configured to use an Always On Availability Group's secondary read-only replica. To resolve this issue, perform whichever of the following actions applies to your version of SharePoint:
 
-- For SharePoint 2007: This is classified as a legacy application. Therefore, SharePoint 2007 cannot be configured to use the `MultiSubnetFailover` parameter. Instead, you have to use the Windows PowerShell command that is described in the [Resolution](#resolution) section.
+- For SharePoint 2007: This is classified as a legacy application. Therefore, SharePoint 2007 can't be configured to use the `MultiSubnetFailover` parameter. Instead, you have to use the Windows PowerShell command that is described in the [Resolution](#resolution) section.
 
 - For SharePoint 2010: Cumulative update packages are now available that add support for the `MultiSubnetFailover` parameter. For more information about the update packages, see the following article:
 
diff --git a/support/sql/database-engine/backup-restore/tde-enabled-database-not-recover.md b/support/sql/database-engine/backup-restore/tde-enabled-database-not-recover.md
@@ -1,20 +1,20 @@
 ---
 title: A TDE-enabled database might not recover
 description: This article provides a resolution for the problem where a TDE-enabled database might not recover when automatic encryption of the master key by the service master key is removed.
-ms.date: 01/14/2021
+ms.date: 05/06/2025
 ms.custom: sap:Database Backup and Restore
 ms.reviewer: VenCher, SureshKa 
 ---
 # A TDE-enabled database might not recover in SQL Server
 
 This article helps you resolve the problem where a TDE-enabled database might not recover when automatic encryption of the master key by the service master key (SMK) is removed.
 
-_Applies to:_ &nbsp; SQL Server 2008 Enterprise, SQL Server 2008 R2 Enterprise  
+_Applies to:_ &nbsp; SQL Server  
 _Original KB number:_ &nbsp; 2666213
 
 ## Symptoms
 
-In Microsoft SQL Server 2008 and in Microsoft SQL Server 2008 R2, a database that's enabled for transparent database encryption (TDE) may not recover. And, the following error message may be logged in the SQL Server error log:
+In Microsoft SQL Server, a database that's enabled for transparent database encryption (TDE) may not recover. And, the following error message may be logged in the SQL Server error log:
 
 > 2012-01-14 22:16:26.47 spid20s Error: 15581, Severity: 16, State: 3.  
 2012-01-14 22:16:26.47 spid20s Please create a master key in the database or open the master key in the session before performing this operation.
@@ -42,7 +42,7 @@ To resolve the issue, enable automatic decryption of the master key. To do this,
 ```sql
 USE MASTER
 GO
-OPEN MASTER KEY DECRYPTION BY PASSWORD = '<password>'
+OPEN MASTER KEY DECRYPTION BY PASSWORD = '******'
 ```
 
 ```sql
diff --git a/support/sql/database-engine/connect/winsock-lsp-network-problem.md b/support/sql/database-engine/connect/winsock-lsp-network-problem.md
@@ -1,15 +1,15 @@
 ---
 title: Winsock LSP may result in network problems
 description: This article helps you resolve the problem that occurs when Winsock Layered Service Providers (LSP) are loaded into SQL Server address space.
-ms.date: 09/25/2020
+ms.date: 05/06/2025
 ms.custom: sap:Database Connectivity and Authentication
 ms.reviewer: SureshKa
 ---
 # Winsock Layered Service Providers may result in network or server stability problems for SQL Server
 
 This article helps you resolve the problem that occurs when Winsock Layered Service Providers (LSP) are loaded into SQL Server address space.
 
-_Original product version:_ &nbsp; Microsoft SQL Server 2005, SQL Server 2008  
+_Original product version:_ &nbsp; Microsoft SQL Server  
 _Original KB number:_ &nbsp; 2033448
 
 ## Symptoms
@@ -42,4 +42,3 @@ If you have a business requirement to use these providers, ensure that you have
 
 - [Winsock architecture](/previous-versions/windows/embedded/ms885821(v=msdn.10))
 - [Transport Service Providers](/windows/win32/winsock/transport-service-providers-2)
-
diff --git a/support/sql/database-engine/database-file-operations/8967-8921-errors-running-dbcc-checkdb.md b/support/sql/database-engine/database-file-operations/8967-8921-errors-running-dbcc-checkdb.md
@@ -1,22 +1,22 @@
 ---
 title: Error when you run the DBCC CHECKDB command
-description: This article provides a workaround for the problem that occurs when you run the DBCC CHECKDB command on a computer that contains a SQL Server database.
-ms.date: 11/03/2020
+description: This article provides a workaround for the problem that occurs when you run the DBCC CHECKDB command on a SQL Server database.
+ms.date: 05/06/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
 ms.reviewer: sureshka, ryanston, sunila, davco
 ---
-# Error message when you run the DBCC CHECKDB command on a computer that contains a SQL Server database
+# Error message when you run the DBCC CHECKDB command on a SQL Server database
 
 This article hepls you work around the problem that occurs when you run the `DBCC CHECKDB` command on a computer that contains a SQL Server database.
 
-_Original product version:_ &nbsp; SQL Server 2008  
+_Original product version:_ &nbsp; SQL Server 2005 and later versions
 _Original KB number:_ &nbsp; 960791
 
 ## Symptoms
 
 Consider the following scenario:
 
-- You restore a Microsoft SQL Server 2008 or SQL Server 2005 database from a backup.
+- You restore a Microsoft SQL Server database from a backup.
 
 - You receive errors during the restore process that prevent you from restoring the database.
 
@@ -42,6 +42,6 @@ This problem occurs if the `DBCC CHECKDB` command cannot perform the necessary c
 
 ## Workaround
 
-To work around this problem, use the TABLOCK hint with the `DBCC CHECKDB` command. This lets the `DBCC CHECKDB` command finish without generating the error message.
+To work around this problem, use the [TABLOCK hint](/sql/t-sql/database-console-commands/dbcc-checkdb-transact-sql#tablock) with the `DBCC CHECKDB` command. This lets the `DBCC CHECKDB` command finish without generating the error message.
 
-For more information about TABLOCK hints, visit the following Microsoft Web site: [Hints (Transact-SQL) - Table](/sql/t-sql/queries/hints-transact-sql-table).
+For more information about TABLOCK hints, see [Hints (Transact-SQL) - Table](/sql/t-sql/queries/hints-transact-sql-table).
diff --git a/support/sql/database-engine/database-file-operations/latch-timeout-running-dbcc-checkdb.md b/support/sql/database-engine/database-file-operations/latch-timeout-running-dbcc-checkdb.md
@@ -1,15 +1,15 @@
 ---
 title: Error when you run the DBCC CHECKDB statement
 description: This article describes a problem where you receive an error message when you try to run the DBCC CHECKDB statement on a database that contains a large table in SQL Server.
-ms.date: 10/11/2022
+ms.date: 05/06/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
 ms.reviewer: keithelm
 ---
 # "Timeout occurred while waiting for latch" error when running `DBCC CHECKDB` statement on a database
 
 This article introduces a problem where you receive an error message when you try to run the `DBCC CHECKDB` statement on a database that contains a large table in SQL Server.
 
-_Original product version:_ &nbsp; SQL Server 2012, SQL Server 2008  
+_Original product version:_ &nbsp; SQL Server  
 _Original KB number:_ &nbsp; 919155
 
 ## Symptoms
@@ -33,29 +33,3 @@ This issue occurs because a time-out occurs when SQL Server traverses the Index
 ## Status
 
 This behavior is by design.
-
-## Applies to
-
-- SQL Server 2008 Developer
-- SQL Server 2008 Enterprise
-- SQL Server 2008 Express
-- SQL Server 2008 Express with Advanced Services
-- SQL Server 2008 R2 Datacenter
-- SQL Server 2008 R2 Developer
-- SQL Server 2008 R2 Enterprise
-- SQL Server 2008 R2 Express
-- SQL Server 2008 R2 Express with Advanced Services
-- SQL Server 2008 R2 Standard
-- SQL Server 2008 R2 Standard Edition for Small Business
-- SQL Server 2008 R2 Web
-- SQL Server 2008 R2 Workgroup
-- SQL Server 2008 Standard
-- SQL Server 2008 Web
-- SQL Server 2008 Workgroup
-- SQL Server 2012 Business Intelligence
-- SQL Server 2012 Developer
-- SQL Server 2012 Enterprise
-- SQL Server 2012 Express
-- SQL Server 2012 Standard
-- SQL Server 2012 Web
-- SQL Server 2012 Enterprise Core
diff --git a/support/sql/database-engine/failover-clusters/cannot-update-cluster-setup-program-checks-rule.md b/support/sql/database-engine/failover-clusters/cannot-update-cluster-setup-program-checks-rule.md
@@ -1,23 +1,23 @@
 ---
 title: Can't update cluster if Setup program checks rule
 description: This article provides a resolution for the problem that occurs when the Setup program checks the Cluster_IsOnlineIfClustered rule.
-ms.date: 10/23/2020
+ms.date: 05/06/2025
 ms.custom: sap:Always On Failover Cluster Instance (FCI)
 ms.reviewer: ramakoni, clivec
 ---
 
-# You can't update a SQL Server 2012 cluster when the Setup program checks the Cluster_IsOnlineIfClustered rule
+# You can't update a SQL Server cluster when the Setup program checks the Cluster_IsOnlineIfClustered rule
 
 This article helps you resolve the problem that occurs when the Setup program checks the `Cluster_IsOnlineIfClustered` rule.
 
-_Original product version:_ &nbsp; SQL Server 2012  
+_Original product version:_ &nbsp; SQL Server 2012 and later versions
 _Original KB number:_ &nbsp; 2817733
 
 ## Symptoms
 
 Consider the following scenario:
 
-- In a cluster environment, you install an instance of Microsoft SQL Server 2012.
+- In a cluster environment, you install an instance of Microsoft SQL Server.
 
 - You try to install SQL Server service packs or cumulative updates on the server that contains this instance.
 
@@ -78,12 +78,3 @@ To identify that this issue is caused by the WMI namespace for the cluster, foll
    >  ```
    >
    > If the issue isn't caused by an invalid MSCluster namespace, the expected result is that the cluster network name is returned.
-
-## Applies to
-
-- SQL Server 2012 Developer
-- SQL Server 2012 Enterprise
-- SQL Server 2012 Express
-- SQL Server 2012 Standard
-- SQL Server 2012 Web
-- SQL Server 2012 Enterprise Core
diff --git a/support/sql/database-engine/install/windows/error-install-sql-server-2008-r2.md b/support/sql/database-engine/install/windows/error-install-sql-server-2008-r2.md
@@ -1,19 +1,19 @@
 ---
-title: Error when you install SQL Server 2008 R2
-description: This article provides a resolution for various errors that occur when you try to install SQL Server 2008 R2.
-ms.date: 10/22/2020
+title: Error when you install SQL Server
+description: This article provides a resolution for various errors that occur when you try to install SQL Server.
+ms.date: 05/06/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
 ---
-# Error message when you try to install SQL Server 2008 R2
+# Error message when you try to install SQL Server
 
-This article helps you resolve various errors that occurs when you try to install SQL Server 2008 R2.
+This article helps you resolve various errors that occurs when you try to install SQL Server.
 
-_Original product version:_ &nbsp; SQL Server 2008 R2
+_Original product version:_ &nbsp; SQL Server  
 _Original KB number:_ &nbsp; 2449398
 
 ## Symptoms
 
-When you try to install Microsoft SQL Server 2008 R2, you receive one or more of the following error messages or experience one or more of the following symptoms. Additionally, you cannot continue with the setup.
+When you try to install Microsoft SQL Server, you receive one or more of the following error messages or experience one or more of the following symptoms. Additionally, you cannot continue with the setup.
 
 Setup error messages or symptoms
 
@@ -105,7 +105,7 @@ To resolve the problem, use one of the following methods:
 
     1. Open Windows Explorer. To do this, click **Start**, click **All Programs**, click **Accessories**, and then click **Windows Explorer**.
 
-    2. Locate and then click the folder: `C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\resources\1033`.
+    2. Locate and then click the folder: `C:\Program Files\Microsoft SQL Server\1XX\Setup Bootstrap\SQLXXX\resources\1033`.
 
     3. Right-click Setup.rll, and then click **Rename**.
 
@@ -126,18 +126,4 @@ To resolve the problem, use one of the following methods:
 
 The error messages that are mentioned in the [Symptoms](#symptoms) section may have other causes. If the steps in the [Resolution](#resolution) section do not resolve the problem, you may be experiencing a different problem.
 
-- For more information about how to install SQL Server 2008 R2, see [How to: Install SQL Server 2008 R2 (Setup)](/previous-versions/sql/sql-server-2008-r2/ms143219(v=sql.105)).
-
-- For more information about known issues when you install SQL Server on Windows 7 or on Windows Server 2008 R2, see [Known issues installing SQL Server on Windows 7 or Windows Server 2008 R2](https://support.microsoft.com/help/955725).
-
-## Applies to
-
-- SQL Server 2008 R2 Datacenter
-- SQL Server 2008 R2 Developer
-- SQL Server 2008 R2 Enterprise
-- SQL Server 2008 R2 Express
-- SQL Server 2008 R2 Express with Advanced Services
-- SQL Server 2008 R2 Standard
-- SQL Server 2008 R2 Standard Edition for Small Business
-- SQL Server 2008 R2 Web
-- SQL Server 2008 R2 Workgroup
+[SQL Server installation guide](/sql/database-engine/install-windows/install-sql-server)
diff --git a/support/sql/database-engine/install/windows/sql-server-not-supported-in-windows-os-where-case-sensitivity-enabled.md b/support/sql/database-engine/install/windows/sql-server-not-supported-in-windows-os-where-case-sensitivity-enabled.md
diff --git a/support/sql/database-engine/search/improve-performance-full-text-queries.md b/support/sql/database-engine/search/improve-performance-full-text-queries.md
diff --git a/support/sql/database-engine/security/sql-2014-fips-140-2-compliant-mode.md b/support/sql/database-engine/security/sql-2014-fips-140-2-compliant-mode.md
