Merge pull request #9112 from HaiyingYu/CI6218&6179

AB#6218 AB#6179 Remove versions, fix broken/redirected links.

Author: HaiyingYu

support/sql/database-engine/availability-groups/alwayson-availability-databases-recovery-pending-suspect.md

@@ -1,7 +1,7 @@
 ---
 title: Always On DB in recovery pending or suspect state 
 description: This article describes the errors and limitations of an availability database in Microsoft SQL Server that is in a Recovery Pending or Suspect state and how to restore the database to full functionality in an availability group.
-ms.date: 04/08/2025
+ms.date: 06/12/2025
 ms.custom: sap:Always On Availability Groups (AG)
 ms.reviewer: ramakoni, cmathews, jopilov
 ---
@@ -10,7 +10,7 @@ ms.reviewer: ramakoni, cmathews, jopilov
 
 This article describes the errors and limitations of an availability database in Microsoft SQL Server that's in a `Recovery Pending` or `Suspect` state and how to restore the database to full functionality in an availability group.
 
-_Original product version:_   SQL Server 2012  
+_Original product version:_   SQL Server  
 _Original KB number:_   2857849
 
 ## Summary
@@ -256,4 +256,3 @@ This method will result in a small outage for applications that are currently co
     ```
 
 3. Recover the damaged database. Then add it and the secondary replica back to the availability group.
-

support/sql/database-engine/database-file-operations/io-subsystem-requirements-tempdb.md

@@ -1,26 +1,21 @@
 ---
 title: I/O subsystem requirements for the tempdb
 description: This article describes the I/O subsystem requirements for the tempdb database in SQL Server.
-ms.date: 09/25/2020
+ms.date: 06/12/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
-ms.reviewer: rdorr
+ms.reviewer: rdorr, jopilov
 ms.topic: article
 ---
 # Microsoft SQL Server I/O subsystem requirements for the tempdb database
 
 This article introduces the I/O subsystem requirements for the tempdb database in SQL Server.
 
-_Original product version:_   Microsoft SQL Server 2005, SQL Server 2008, SQL Server 2012 SQL Server 2014  
+_Original product version:_   Microsoft SQL Server  
 _Original KB number:_   917047
 
 ## Summary
 
-Microsoft SQL Server requires that the I/O subsystem used to store system and user databases fully honor Write-Ahead Logging (WAL) requirements through specific I/O principals. These requirements are necessary in order to honor the ACID properties of transactions: Atomic, Consistent, Isolated, and Durable. Details about I/O subsystem compliance requirements are provided in the following references:
-
-SQL Server 2000 I/O basics [https://technet.microsoft.com/library/cc966500.aspx](/previous-versions//cc966500(v=technet.10))
-
-> [!NOTE]
-> This article also applies to SQL Server 2005 and later versions.
+Microsoft SQL Server requires that the I/O subsystem used to store system and user databases fully honor Write-Ahead Logging (WAL) requirements through specific I/O principals. These requirements are necessary in order to honor the ACID properties of transactions: Atomic, Consistent, Isolated, and Durable. Details about I/O subsystem compliance requirements are provided in [SQL Server I/O basics](/previous-versions//cc966500(v=technet.10)).
 
 The following list is a quick summary of the requirements:
 
@@ -54,7 +49,7 @@ To guarantee the success of the recovery processes, such as rollback and crash r
 The storage location for the tempdb database must act in strict accordance with established disk drive protocols. In all ways, the device on which the tempdb database is stored must appear and act as a physical disk providing read after write capabilities. Transaction sector rewrite operations may be an additional requirement of specific implementations. For example, SQL Server does not support database modifications by using NTFS file system compression because NTFS compression can rewrite sectors of the log that have already been written and considered hardened. A failure during this type of rewrite can cause the database to be unusable, damaging data that SQL Server already considered secure.
 
 > [!NOTE]
-> SQL Server 2005 extended support or compression to read only databases and file groups. See the SQL Server 2005 Books Online for complete details.
+> SQL Server extended support or compression to read only databases and file groups. See the SQL Server Books Online for complete details.
 
 Transactional sector rewrite operations are pertinent to all SQL Server databases that include the tempdb database. A growing variety of extended storage technologies use devices and utilities that can rewrite data that SQL Server considers secure. For example, some of the emerging technologies perform in-memory caching or data compression. In order to avoid severe database damage, any sector rewrite must have full transactional support in such a way that if a failure occurs, the data is rolled back to the previous sector images. This guarantees that SQL Server is never exposed to an unexpected interruption or data damage condition.
 
@@ -100,7 +95,7 @@ An application should tune to remove unnecessary and unwanted sorts and hashes t
 
 The benefits of putting the tempdb database on a high-speed system can only be determined through rigorous testing and measurements of the application workloads. The workload has to be studied carefully for the characteristics that the tempdb database may benefit from, and the I/O safety must be confirmed before deployment.
 
-The sort and hash operations work together with the SQL Server memory managers to determine the size of the in-memory scratch area for each sort or hash operation. As soon as the sort or hash data exceeds the allocated in-memory scratch area, data may be written to the tempdb database. This algorithm has been expanded in SQL Server 2005, reducing the tempdb database usage requirements over earlier versions of SQL Server.
+The sort and hash operations work together with the SQL Server memory managers to determine the size of the in-memory scratch area for each sort or hash operation. As soon as the sort or hash data exceeds the allocated in-memory scratch area, data may be written to the tempdb database. This algorithm has been expanded in SQL Server, reducing the tempdb database usage requirements over earlier versions of SQL Server.
 
 > [!CAUTION]
 > SQL Server is designed to account for memory levels and current query activities when making query plan decisions that involve the use of tempdb database operations. Therefore, the performance gains vary significantly based on workloads and application design. We strongly recommend that you complete testing with the preferred solution to determine possible gains and evaluate I/O safety requirements before such a deployment.
@@ -180,15 +175,13 @@ Microsoft doesn't certify or validate that third-party products work correctly w
 
 ## References
 
-For more information, see the following Microsoft Knowledge Base articles:
-
-- [Additional SQL Server diagnostics added to detect unreported I/O problems](https://support.microsoft.com/help/826433)
+For more information, see:
 
 - [Error message 823 may indicate hardware problems or system problems in SQL Server](/sql/relational-databases/errors-events/mssqlserver-823-database-engine-error)
 
 - [Using disk drive caching with SQL Server](https://support.microsoft.com/help/234656)  
 
-- [Description of support for network database files in SQL Server](https://support.microsoft.com/help/304261)
+- [Description of support for network database files in SQL Server](./support-network-database-files.md)
 
 - [Microsoft does not certify that third-party products will work with Microsoft SQL Server](https://support.microsoft.com/help/913945)
 
@@ -197,3 +190,5 @@ For more information, see the following Microsoft Knowledge Base articles:
 - [Optimizing Your Query Plans with the SQL Server 2014 Cardinality Estimator](/previous-versions/dn673537(v=msdn.10))
 
 - [Query Performance](/previous-versions/sql/sql-server-2008-r2/ms190610(v=sql.105))
+
+- [SQL Server Database Engine Disk Input/Output (I/O) requirements](./database-engine-input-output-requirements.md)

support/sql/database-engine/database-file-operations/logging-data-storage-algorithms.md

@@ -1,13 +1,13 @@
 ---
 title: Logging and data storage algorithms
 description: This article discusses how SQL Server logging and data storage algorithms extend data reliability.
-ms.date: 10/10/2022
+ms.date: 06/12/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
-ms.reviewer: rdorr, bobward
+ms.reviewer: rdorr, bobward, jopilov
 ---
 # Description of logging and data storage algorithms that extend data reliability in SQL Server
 
-_Original product version:_   SQL Server 2014, SQL Server 2012, SQL Server 2008, SQL Server 2005  
+_Original product version:_   SQL Server  
 _Original KB number:_   230785
 
 ## Summary
@@ -185,7 +185,7 @@ Microsoft has performed testing on several SCSI and IDE drives by using the `SQL
 
 For more information about the `SQLIOSim` utility, see the following article in the Microsoft Knowledge Base:
 
-[How to use the SQLIOSim utility to simulate SQL Server activity on a disk subsystem](https://support.microsoft.com/help/231619)
+[How to use the SQLIOSim utility to simulate SQL Server activity on a disk subsystem](../../tools/sqliosim-utility-simulate-activity-disk-subsystem.md)
 
 Many computer manufacturers order the drives by having the write cache disabled. However, testing shows that this may not always be the case. Therefore, always test completely.
 
@@ -266,5 +266,5 @@ COMMIT TRAN
 GO
 ```
 
-SQL Server requires that systems support **guaranteed delivery to stable media**, as described in the [SQL Server I/O Reliability Program Review Requirements](https://download.microsoft.com/download/f/1/e/f1ecc20c-85ee-4d73-baba-f87200e8dbc2/sql_server_io_reliability_program_review_requirements.pdf) download document. For more information about the input and output requirements for the SQL Server database engine, see
-[Microsoft SQL Server Database Engine Input/Output Requirements](https://support.microsoft.com/help/967576).
+SQL Server requires that systems support **guaranteed delivery to stable media**. For more detailed information, see
+[Microsoft SQL Server Database Engine Input/Output Requirements](./database-engine-input-output-requirements.md).

support/sql/database-engine/install/windows/permission-error-use-volume-mount-point.md

@@ -1,20 +1,20 @@
 ---
 title: Permission error when you use a volume mount point
 description: This article provides a resolution for the problem that occurs when you assign a root folder of the volume mount point to the SQL Server system folders.
-ms.date: 11/04/2020
+ms.date: 06/12/2025
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
-ms.reviewer: mide
+ms.reviewer: mide, jopilov
 ---
 # Permission error occurs when you use a volume mount point in SQL Server Setup
 
 This article helps you resolve the problem that occurs when you assign a root folder of the volume mount point to the SQL Server system folders.
 
-_Original product version:_   SQL Server, Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Standard  
+_Original product version:_   SQL Server, Windows Server Datacenter, Windows Server Standard
 _Original KB number:_   2867841
 
 ## Symptoms
 
-When you install Microsoft SQL Server on Windows Server 2012, the installation fails if you assign a SQL Server system folder (such the DATA or LOG files location) to a volume mount point root folder. Additionally, you receive the following error message:
+When you install Microsoft SQL Server on Windows Server, the installation fails if you assign a SQL Server system folder (such the DATA or LOG files location) to a volume mount point root folder. Additionally, you receive the following error message:
 
 > While updating permission setting for folder 'T:\DATA\System Volume Information' the permission setting update failed for file 'T:\DATA\System Volume Information\ResumeKeyFilter.Store'. The folder permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
 
@@ -28,4 +28,4 @@ To resolve this problem, create a subfolder in the volume mount point, and assig
 
 ## More information
 
-When SQL Server Setup configures SQL Server system folders, Setup tries to change the permissions of folders and the files that are in those folders. But if you set the system folders to a root folder of the volume mount point, the `\System Volume Information\ResumeKeyFilter.Store` file is created on Windows Server 2012. SQL Server Setup cannot change the permissions of `ResumeKeyFilter.Store` because SYSTEM is the only permission that is set on this file.
+When SQL Server Setup configures SQL Server system folders, Setup tries to change the permissions of folders and the files that are in those folders. But if you set the system folders to a root folder of the volume mount point, the `\System Volume Information\ResumeKeyFilter.Store` file is created on Windows Server. SQL Server Setup cannot change the permissions of `ResumeKeyFilter.Store` because SYSTEM is the only permission that is set on this file.

support/sql/database-engine/performance/recommended-updates-configuration-options.md

@@ -1,14 +1,14 @@
 ---
 title: Recommended updates and configuration options
-description: This article includes a list of performance improvements and configuration options that are available for SQL Server 2012 and later versions.
-ms.date: 09/14/2020
+description: This article includes a list of performance improvements and configuration options that are available for SQL Server 2014 and 2012.
+ms.date: 06/12/2025
 ms.custom: sap:SQL resource usage and configuration (CPU, Memory, Storage)
-ms.reviewer: ramakoni, Sureshka
+ms.reviewer: ramakoni, Sureshka, jopilov
 ms.topic: how-to
 ---
-# Recommended updates and configuration options for SQL Server with high-performance workloads
+# Recommended updates and configuration options for SQL Server 2014 and 2012 with high-performance workloads
 
-This article includes a list of performance improvements and configuration options that are available for SQL Server 2012 and later versions.
+This article includes a list of performance improvements and configuration options that are available for SQL Server 2014 and SQL Server 2012.
 
 _Original product version:_   SQL Server 2014, SQL Server 2012  
 _Original KB number:_   2964518
@@ -73,7 +73,7 @@ Review the content in the Knowledge Base article/Books Online Resource column an
 | [Slow Performance on Windows Server when using the "Balanced" Power Plan](https://support.microsoft.com/help/2207548) |Review the article, and work with your Windows administrator to implement one of the solutions that are noted in the "Resolution" section of the article.|
 | |Manually assign NUMA nodes to K-groups. |
 | [Optimize for ad hoc workloads](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) [FORCED PARAMETERIZATION](/sql/relational-databases/query-processing-architecture-guide#ForcedParamGuide)| Entries in the plan cache are evicted because of growth in other caches or memory clerks. You might also encounter plan cache eviction when the cache reaches its maximum number of entries. In addition to trace flag 8032 discussed above, consider the [optimize for ad hoc workloads](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) server option and also the [FORCED PARAMETERIZATION](/sql/relational-databases/query-processing-architecture-guide#ForcedParamGuide) database option. |
-| [How to reduce paging of buffer pool memory in SQL Server](https://support.microsoft.com/help/918483) [Memory configuration and sizing considerations in SQL Server 2012 and later versions](https://support.microsoft.com/help/2663912/) |Assign the [Enable the Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) user right to the SQL service Startup account. See [How to enable the "locked pages" feature in SQL Server 2012](https://support.microsoft.com/help/2659143/). Set maximum server memory to approximately 90 percent of total physical memory. Make sure that the [Server memory configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options) setting accounts for memory from only the nodes that are configured to use affinity mask settings.|
+| [How to reduce paging of buffer pool memory in SQL Server](https://support.microsoft.com/help/918483) |Assign the [Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) user right to the SQL service Startup account. Set maximum server memory to approximately 90 percent of total physical memory. Make sure that the [Server memory configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options) setting accounts for memory from only the nodes that are configured to use affinity mask settings.|
 | [SQL Server and Large Pages Explained...](/archive/blogs/psssql/sql-server-and-large-pages-explained) [Tuning options for SQL Server when running in high performance workloads](https://support.microsoft.com/help/920093)| Consider enabling TF 834 if you have a server with a large amount of memory, particularly with an analytical or data warehousing workload. Keep in mind that [TF 834 is not recommended if you are using columnstore indexes](https://support.microsoft.com/kb/3210239). |
 | [Description of the "access check cache bucket count" and "access check cache quota" options that are available in the sp_configure stored procedure](/sql/database-engine/configure-windows/access-check-cache-server-configuration-options)|Use [access check cache Server Configuration Options](/sql/database-engine/configure-windows/access-check-cache-server-configuration-options) to configure these values per the recommendations in the Knowledge Base article. Recommended values for high-end systems are as follows:<br/>"access check cache bucket count": 256<br/>"access check cache quota": 1024<br/> <br/>|
 | [ALTER WORKLOAD GROUP](/sql/t-sql/statements/alter-workload-group-transact-sql) [Memory grant query hints](https://support.microsoft.com/help/3107401)| If you have many queries that are exhausting large memory grants, reduce `request_max_memory_grant_percent` for the default workload group in the resource governor configuration from the default 25 percent to a lower value. New query memory grant options are available (`min_grant_percent` and `max_grant_percent`) in SQL Server |