Many of my previous posts do talk a lot about how CHECKDB works within SQL Server with various interesting combination of scenarios. Though the use of CHECKDB and understanding of this topic is quite complex, in this post let me talk about the undocumented option of TABLERESULTS. It is quite handy and I used it in one of the demo at TechEd India 2010.
This option will allow CHECKDB to return a TDS based result set for all messages (informational and errors) returned as part of executing CHECKDB. This option maybe undocumented for multiple reasons:
* Maybe the code is not yet tested or there can be bugs that can disrupt the behavior end-users want.
The option is interesting as the result set if implemented fully could help produce a report of true errors encountered, specific repair actions needed for each error, etc.
The command is beneficial to analyze corrupt databases when brought in-house for troubleshooting. Esp for cases when there is corrupt index pages, you can quickly look at the INDID and figure out is they are only non-clustered indexes that have got damaged or if there are Clustered indexes also which have to be examined …
Microsoft is not under any obligation to provide information or support these commands or tools as these are undocumented. My previous posts around CHECKDB are –
This entry was posted on Friday, May 28th, 2010 at 10:23 and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.