Since it's not usually a major issue, and can't be fixed while SQL's running, and it pretty immaterial on a SAN, not really.

But it you want. Google: file system fragmentation

It's...

Never heard the term 'data fragmentation'. Guess the person meant index fragmentation, because data can only be fragmented when it's in an index. (unless they meant data file fragmentation, which...

Restore from a good backup

And do some investigation of that IO subsystem, maybe move the DB elsewhere (different disks)

Post the output you got (everything). I can't tell anything from a description of the messages. (no, not with tablock)

Repair is not the recommended way to fix corruption, it's for...

kevin.kembel (1/2/2013)

---

So in your article where you showed the data persisting to disk when there was no memory pressure, that was because it was convenient for SQL at the time...

opc.three (1/2/2013)

---

GilaMonster (1/2/2013)

---

No.

I thought a rebuild would re-scan the clustered same as a drop+recreate which would work since all inconsistencies were found in the...

Daily? So up to 24 hours of data loss is acceptable?

Log backups are usually a lot more frequent than that,...

RAM-only table-variables are indeed a myth.

Table variables (like temp tables) will be in memory if possible and written to disk if not. They are always allocated space in TempDB, whether...

CheckDB doesn't check the log file, so it wouldn't pick up the corruption.

Usual solution given for this case:

Restore a backup, full, and logs

Or, if you don't have backups (or can't...

No.

Nope....

Read the article again.

If your log is continually growing it's because you're mis-managing it. Most likely full recovery model with no log backups. Read the article, make sure you have...

Please read through this - Managing Transaction Logs[/url]

Don't rebuild the index. It'll likely fail. Drop the index and recreate it.

Why do I have to wait til May?

Restore from a clean backup, that's not repairable in any way.