<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage Error on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/storage-error/</link><description>Recent content in Storage Error on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/storage-error/index.xml" rel="self" type="application/rss+xml"/><item><title>Detect Suspect Database Pages with msdb.dbo.suspect_pages</title><link>https://www.sqlserver70.com/post/sql-server-suspect-database-pages-detection-script/</link><pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/sql-server-suspect-database-pages-detection-script/</guid><description>
&lt;p&gt;Storage errors do not always surface as immediate failures. When SQL Server encounters an 823, 824, or 825 error reading or writing a database page, it records the offending page in &lt;code&gt;msdb.dbo.suspect_pages&lt;/code&gt; — a system table that accumulates page-level I/O failures across service restarts. Querying this table is the fastest first-pass for any corruption investigation, answering whether bad pages exist and which databases are affected before committing to a full &lt;code&gt;DBCC CHECKDB&lt;/code&gt; run.&lt;/p&gt;</description></item></channel></rss>