CHECKDB returns no errors but suspect pages does

• webrunner

  SSC-Dedicated

  Points: 31989

  More actions

  September 29, 2022 at 3:28 pm

  #4093468

  Hello experts,

  I ran sp_Blitz and on a dev server and saw two results indicating corruption.

  I then ran the following after Googling how to see the corrupted data:

  SELECT DB_NAME(database_id), * FROM msdb.dbo.suspect_pages

  That returns 3 rows at the moment, including 2 rows for the db "mydb." But I also found a way to run CHECKDB for mydb with table results and no info msgs to make it easier to read.

  DBCC CHECKDB ('mydb') WITH NO_INFOMSGS, TABLERESULTS

  That returns nothing.

  Does anyone know why that is? I was hoping to see correlation with the suspect pages query. My biggest concern at the moment is if something like this happens in production I won't know how to rely on the results of the queries.

  Thanks for any help.

  -- webrunner

  • This topic was modified 2 years, 8 months ago by webrunner.

  -------------------
  A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
  Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

• Ed B

  Hall of Fame

  Points: 3685

  More actions

  September 29, 2022 at 5:01 pm

  #4093523

  What is the event_type of those suspect pages? Could they have been fixed already?

• webrunner

  SSC-Dedicated

  Points: 31989

  More actions

  September 29, 2022 at 5:44 pm

  #4093554

  Hi Ed,

  Thanks. The even types are:

  mydb1: event types 4 and 2

  mydb2: event type 3

  According to the MS documentation, those mean:

  2 = Bad checksum.

  3 = Torn page.

  4 = Restored (page was restored after it was marked bad).

  I guess maybe 4 is already fixed? But not sure about the others. Thanks for any additional insight.

  -- webrunner

  -------------------
  A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
  Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html