Merge pull request #7966 from MicrosoftDocs/UpdateDbccCheckdbDiags-pijocoder-010225

AB#3272: Add a bit more information on how to investigate hardware issues and also RAM

Author: sevend2

support/sql/database-engine/database-file-operations/troubleshoot-dbcc-checkdb-errors.md

@@ -2,7 +2,7 @@
 title: Troubleshoot database consistency errors reported
 description: This article introduces how to troubleshoot errors reported by the DBCC CHECKDB command.
 ms.reviewer: jopilov, v-jayaramanp
-ms.date: 08/13/2024
+ms.date: 01/03/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
 ---
 
@@ -38,7 +38,7 @@ The cause of these problems can range from file system corruption, underlying ha
 
 ## Resolution
 
-1. Resolve any underlying hardware-related problems on the system before you proceed with restoring a backup or otherwise repairing the database. Apply any device driver, firmware, BIOS, and operating system updates that are relevant to the I/O path. Work with the administrator of the full I/O path (local machine, device drivers, storage NICs, SAN, backend storage, and cache) to isolate and resolve any problems. Examples include updating device drivers and checking configuration of the entire I/O path. For more information about checking the root cause, see [Investigate root cause](#investigate-root-cause-for-database-consistency-errors).
+1. Resolve any underlying hardware-related problems on the system before you proceed with restoring a backup or otherwise repairing the database. Apply any device driver, firmware, BIOS, and operating system updates that are relevant to the I/O path. Work with the administrator of the full I/O path (local machine, device drivers, storage NICs, SAN, backend storage, and cache) and memory (RAM) to isolate and resolve any problems. Examples include updating device drivers and checking the configuration of the entire I/O path. For details on how to investigate the root cause, see [Investigate root cause](#investigate-root-cause-for-database-consistency-errors).
 1. If `DBCC CHECKDB` reports permanent consistency errors, the best solution would be to restore data from a known good backup. For more information, see [Restore and Recovery](/sql/relational-databases/backup-restore/restore-and-recovery-overview-sql-server).
 1. Apply the latest SQL Server Cumulative Update or Service Pack to make sure you aren't running into any known issues. Check the [Cumulative Update or Service Pack documentation](../../releases/download-and-install-latest-updates.md) for any known issues fixed related to database corruption (consistency errors) and apply any relevant fixes. One central location where you can search for all fixes for a particular version if the [Detailed fix lists for SQL Server 2022, 2019, 2017](https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fdownload.microsoft.com%2Fdownload%2Fd%2F3%2Fe%2Fd3e28f3d-6a4f-47ce-aaa5-9d74c5590ed6%2FSQLServerBuilds.xlsx).
 1. If the `DBCC CHECKDB` errors are intermittent, that is if they appear on one run and disappear on the next one, you might be facing disk cache issues (either device driver or other I/O path issue). Work with the maintainers of the I/O path to isolate and resolve any problems. Examples include updating device drivers, checking configuration of the entire I/O path, and updating firmware and BIOS on the I/O path devices and system.
@@ -81,7 +81,7 @@ The cause of these problems can range from file system corruption, underlying ha
 To identify the root cause of database consistency errors, consider these methods:
 
 - Check the Windows System Event Log for any system level, driver, or disk-related errors and work with your hardware manufacturer to resolve them.
-- Run any diagnostics provided by your hardware manufacturers for the computer and/or disk system.
+- Run any diagnostics provided by your hardware manufacturers for the computer and/or disk system. Most systems provide BIOS/UEFI built-in diagnostics for storage (hard drives), memory, CPUs, system boards, RAID arrays, and multiple other components. 
 - Work with your hardware vendor or device manufacturer to make sure that:
   - The hardware devices and the configuration confirm to the [Microsoft SQL Server Database Engine Input/Output requirements](database-engine-input-output-requirements.md).
   - The device drivers and other supporting software components of all devices in the I/O path are updated.