Yup - looks like it.

It's usually indicative of some kind of corruption, possibly transient. Run DBCC CHECKDB on the database concerned. If it doesn't turn up anything, it could be a transient problem in...

So definitely sounds like a transient IO problem. Run IO diagnostics and the SQLIOSim tool to help flush out any IO issues you may have.

Thanks

Have you run CHECKDB on master?

Looks like a transient problem in the IO subsystem if the issue goes away and comes back - e.g. a stale read from a disk...

Duplicate post...

ok - we're already going back/forth on this in email - you're not going to get a different answer here.

You need to use the WITH TABLOCK option. You've got a...

Just the number of files.

Thinking about it more - even if you can hack it into the system, the database still won't startup as it will hit the same problem...

Parallelism doesn't have anything to do with it on 2005. The problem comes because of a disk or memory corruption that alters a page ID (2-byte file number + 4...

The file header page (first page in the file) is corrupt - you will not be able to attach this directly. You *might* be able to use the hack method...

Hi,

This is a clustered index that it's repairing by deleting pages at the leaf-level - essentially deleting a bunch of records. The pages look to be trashed so there's nothing...

Absolutely - 2000 and 7.0 both had essentially the same allocation sub-system in the Storage Engine as 2005.

Wilfred van Dijk (6/8/2008)

---

If you rebuild your indexes, and don't have the option SORT_IN_TEMPDB, SQL will build the new index in the same filegroup of the original index in these...

Well here's the thing - if CHECKDB says that you need to use REPAIR_ALLOW_DATA_LOSS, then it's going to lose data because the way it repairs things is to delete the...

Bummer. I've seen this quite a few times where there's no way to clear the spid except to reboot.

My guess is that its complaining about the USE statement?