Agreed - and I just replied to your thread on sqlteam.com with the same advice too.

Paresh Prajapati (1/17/2009)

Paul Randal (1/17/2009)

Paresh Prajapati (1/16/2009)

Please...

Paresh Prajapati (1/16/2009)

Please take a tail log...

Fraid not.

Just got back a couple of days ago.

The PK errors are because repair takes no account of any constraints when it does repairs - it's just making the database physically...

This is a case where you're not going to be able to get any further than restoring the first backup using CONTINUE_AFTER_ERROR. The log is damaged in such a way...

You've got corrupt pages in some of the critical system tables - this is why CHECKDB fails right away. These were most likely cause by the bad RAID controller you...

Hmm - haven't heard of this and it shouldn't happen. It can deadlock with user updates but then it should be chosen as the deadlock victim. I'd call Product Support...

Hey George - I had a thought - can you try changing the setting of NUMERIC_ROUNDABORT and see if CHECKTABLE completes? If it does, you might be able to find...

I'd try doing it in ranges, to limit the result set in each case. I'm not sure whether you'll get an indication of which row failde - at least with...

So it looks like you've got some corrupt data values in the table - can you select * all the data without any errors? My guess is that one or...

Try changing the setting of arithabort when you have quoted_identifier on... what happens?

I think its arithabort that's causing you problems - there's a section in Books Online called Session Settings That Affect Results - look in there. The problem isn't DBCC, its...

Right - you've got a computed column in the table and the SET options have to be on correctly for DBCC CHECKDB to run.

Thanks

Probably this bug Corruption bug that people are hitting: Msg 8914 - PFS free space