Gail asked me to chime in here.

The sysindexes errors are corruptions in the statistics blobs - you should be able to get around those by dropping and recreating all your...

Yes. Imagine a single bit corruption in the middle of a varchar column. Without a page checksum, nothing will detect the corruption.

Check this out: Importance of having the right backups

You shouldn't be rebuilding the log - you're going to cause corruption and data loss that way. See Corruption: Last resorts that people try first....

It's likely that something in the...

Wow - I was watching for updates on the original thread you started so missed all of this.

The FCB wait you saw is because you have activity going on on...

You should really start a new thread for each new issue.

Your database has IO-susbsystem caused corruption in it. Run DBCC CHECKDB (yourdb) WITH ALL_ERRORMSGS, NO_INFOMSGS to find out the extent...

ok - best bet is to call Product Support to help work out what's wrong - we're not going to be able to do it over the forums. Let us...

ok - I've rewritten the blog post to be clearer - let me know what you think - good or bad. Cheers

I know where you're coming from - no offense taken!

Interesting - my article is specifically about how it *wasn't* a SQL Server problem - but how bad schema/design/testing led to...

Latest I've heard from the SQL team today is that the absolute root-cause is still being investigated.

And also, if it turns out that what was reported originally was BS, I did caveat my blog post by saying "Now, this is slight conjecture, as I don't know...

I know - see the edit in the post above - I thought I'd deleted it right away as it's wrong.

Yes, it was a capacity planning issue because they hadn't tested the schema for that load. As soon as they rebuilt the clustered index to remove the fragmentation, things sped...

Is this on 2000? If so, emptied pages in heaps don't necessarily get deallocated (freed).

Try one of: truncate table, creating a clustered index (and maybe keeping it around or dropping...

I'm guessing that's your problem then. They've just announced support for Lock Pages In Memory for 32-bit - should be out in the next month or two. See here.

[Edit: thought...