DBCC CHECKDB’s NOINDEX Option

Kendra Little explains the NOINDEX option of DBCC CHECKDB and how it relates to PHYSICAL_ONLY:

PHYSICAL_ONLY looks at page structures and makes sure something isn’t obviously wrong. If you have the database’s page verification option set to CHECKSUM (the default since SQL Server 2005, and a very good thing), it runs a checksum on the page and compares it to a checksum recorded in the header when the page was last modified.

When you use the PHYSICAL_ONLY option, you’re telling SQL Server to skip logical checks. It won’t do things like make sure the data in a clustered and nonclustered index on a table is consistent with one another.

I like the analogy, as well as the how-to guide on messing up your database.  But try not to do that to a production database…

Related Posts

A Story Of Database Corruption

Jason Brimhall tells a tale of a corrupt database: Calmly, you settle in and check the server and eventually find your way to the error logs to see the following: Msg 823, Level 24, State 2, Line 1 The operating system returned error 1(Incorrect function.) to SQL Server during a read at offset 0x0000104c05e000 in file […]

Read More

Parallel CHECKDB

Kevin Feasel

2017-12-19

DBCC

Arun Sirpal shows us when DBCC CHECKDB can go parallel: DBCC CHECKDB has the ability to perform parallel checking of objects. However, it absolutely depends on the edition of SQL Server, it only happens when using enterprise edition. Let’s see this in action. I propose the following tests for this blog post: Test on a […]

Read More

Categories

August 2016
MTWTFSS
« Jul Sep »
1234567
891011121314
15161718192021
22232425262728
293031