When you have an instance of the corruption, post the output from CHECKDB please so we can see what the corruption is. Could be a number of different things -...

Which SP and CU of 2005 are you using? Looks like a bug has been introduced that is suppressing the repair level output when a 2570 is present - it...

No - it will still say repair_allow_data_loss, and most especially because of the corrupt clustered index.

Is the database read-only? Or are you running CHECKDB against an explicitly-created database snapshot?

How exactly...

Neither of the suggested workarounds are good. The WITH TABLOCK will most likely fail as it needs an exclusive database lock to be able to perform the allocation checks –...

Most likely your IO subsystem.

With a heap it's very hard to tell what data will be lost - impossible for you as you don't have a clean backup.

No, no alternative.

Either restore from your backups or run repair_allow_data_loss and you will lose a page of data from the Schedule table, with whatever effect that will have on your application.

The only place to get that from is in the output from repair - it tells you which pages are being deallocated.

See my first response...

update master..sysdatabases

set status = status + 32768

where name ='My_database'

go

Not guaranteed to work at all in SQL 2000.

Well, you could follow the advice I gave you in email a couple of hours ago... there's basically nothing to be done except to take the database back to a...

There are no disadvantages to that situation - which is why I wrote DBCC CHECKDB that way. There's no alternative to having the deallocated pages be part of the data...

Which is why I gave that caveat to start with. If there are active transactions, just go into EMERGENCY mode and rebuild the log - but then you're looking at...

First issue: your IO subsystem corrupted the file header of the transaction log - get your IO subsystem checked out and fixed.

To your question: yes, but not without an element...

No - you can't 100% infer that. With 8 instances installed on a 4GB memory server, you're going to run into memory constraints and you may still have issues like...

Yup - I think this table is just too big for the memory limitations of Express under pressure from the other instances on the box. Splitting things up should allow...