You're welcome. What a shame - I'd have liked to see the corrupt data (I'm strange that way :))

Hey Igor,

There were a couple of bugs in this space in 2000 but nothing in 2005 SP2 that I know of. Can you post the entire output of CHECKDB with...

Yup - should be no reason why a full restore of all the log shouldn't work UNLESS the corrupt data was somehow picked up and used (thus causing second order...

My 8000 byte example was just that - an example. It doesn't need 8192 bytes for *each* 8000 byte chunk of a larger value. 8040 bytes of data can be...

It's not a problem with Reporting Services - its a corruption in the database that RS is using.

What's the output from a DBCC CHECKDB on the database? Do you have...

Are you taking into account the overhead of storing the files in a database? Storing, say, 8000 bytes of compressed data in an IMAGE field requires an 8192 byte database...

You've got a bunch of corruption.

You have two options for getting rid of it:

1) restore from your backups

2) run REPAIR_ALLOW_DATA_LOSS

#1 is by far the preferred option as you will minimize...

Actually its not that complex. There's a single page that's corrupt - page (1:218) - and it happens to be the head of an IAM chain, which is leading to...

What error do you get if you try to manually attach the database?

Your best bet is probably to hack the database back into the server (create a dummy database of...

Hi Teresita,

First off, you're running 2000, not 2005 (this forum) - the 602 error message you posted is the 2000 version. The sysindexes table is corrupt - it can't find...

Ah - so you ran CHECKTABLE before CHECKDB. It's entirely possible that the corruption occured between the time you ran CHECKTABLE and the time you ran CHECKDB. Does CHECKTABLE now...

Come to think of it - that error isn't one that will ever be falsely reported. If the error is still reported by CHECKDB then it should be seen by...

CHECKTABLE should find the same error on the table as CHECKDB, unless the page has since changed in the database (if there's any workload running), or you run into one...

One more thing to check - is the database in FULL recovery mode? If so, your log file will continue to grow unless you take log backups...

Looks like you've hit this page corruption during a transaction rollback or crash recovery. There's no good way out of this on 2000 except to restore from a backup. Your...