OK. Doing the shrink (aggressively, as much as possible), and then afterward, checking for corruption (still there), and THEN running DBCC CheckDB r-a-d-l did the trick -- all in SQL...

Well darn you Paul. I hate it when I'm wrong. 🙂

OK...so I went back and questioned this guy this AM, and followed his steps, and turns out he had grabbed...

I'll talk to the guy who did it tomorrow.

I questioned the backup/restore, I didn't think that would work from 2005 to 2000.

I do know that if you leave the DB...

Tried backing up from SQL 2000 and restoring to SQL 2008, no dice. Restored in suspect mode.

Next step, take backup and restore to SQL 2000, detach the mdf and ldf,...

Since there is 24 GB of memory, and the DB is only 8 GB -- and, I am seeing really fast response time on the disk, I think it cannot...

Old Box (SQL 2000, Windows 2003)

Table 'foo', Scan count 1, logical reads, 6346, physical reads 0, read-ahead reads 0.

New Box (SQL 2008, Windows 2008 R2)

Table 'foo', Scan count 1, logical...

The shrink didn't do the trick.

Next step will be to try the SQL 2005 "fixer upper"

I'll let you know how it goes.

Thanks again so much.

🙂

Very satisfying answer. OK. I will try the shrink, and then try having them restore a backup to SQL 2005 and see if I can fix it there. If it...

Oh, and should have mentioned, this is SQL 2000 sp4.