We're talking about table corruption here. The real crux of the matter was 'rebuilding indexes' being offered as a solution without demonstrating understanding of the problem. All caps and asterisks...

A 2000 CHECKDB won't show problems because I didn't add all the data purity code until 2005.

Dude - they're 2570 data purity errors. Rebuilding indexes is **NEVER** a solution for fixing corruption. You're wrong. Move on.

And yet you recommended a solution with no idea what the problem is?

He(?) clearly stated its a data purity error - which finds invalid data for columns with data types...

ALZDBA - Can you explain what dropping adn recreating the indexes will do, apart from waste time and disk space?

djrgreene - you need to have a value that you can...

Good stuff Jason.

@medelstein From the (incredibly helpful, eh?) error, you're running the code on a SQL 2000 box, or in the context of a DB that set to the 8.0...

It won't do anything to help you. The reason why I got it to say what the minimum repair level is, is because that's what you'll need to run for...

Folks - this is another questions written by Kimberly - not sure why it's posted under my account instead of hers.

SharePoint's tricky, because allowing CHECKDB to delete some rows in the AllDocStreams table could mean you lose documents, potentially 'corrupting' the search database too and causing SharePoint failures.

You've got one...

Do you have any index maintenance that runs nightly, or is the data in the tables very volatile? I think you're seeing 'disappearing corruptions' - real corruptions but the pages...

Picking up the thread here, can you share some of the CHECKDB output please? Were the checksum failures re-appearing on the same databases? Are the databases stored on the same...

Can you run DBCC CHECKTABLE on sysobjects, sysindexes, syscolumns please?

Yes, saw that while reading the thread - and that's why I'm...

Either someone's messed with the system tables or there's more output from checkdb. Can you post the complete output of:

dbcc checkdb (yourdbname) with all_errormsgs, no_infomsgs

Thanks

Don't do that. I strongly advise you to call Product Support who will stay with you on the phone while you sort this out - no disrespect, but with the...