GilaMonster (2/2/2015)

---

In that case, since you have no clean backup, you're going to have to drop and recreate the table. If the data's important, you should be able to do...

Yes that's all that is output. Unless I am missing something obvious.

GilaMonster (1/30/2015)

---

Database 19 will probably be the hidden snapshot that CheckDB creates.

To be honest, I suspect dropping the table will be about the only solution here, although I'd like to...

GilaMonster (1/30/2015)

---

If the metadata is corrupt, you're not going to be able to drop the index, no matter what commands you try.

Before trying any more shotgun approaches...

Do you have a...

ScottPletcher (1/29/2015)

---

Dell Dude (1/29/2015)

---

ScottPletcher (1/29/2015)

---

So I guess the table name is "elmah"?! It's somewhat confusing with all the different "table names" given.

DROP INDEX PK_ELMAH_Error...

ScottPletcher (1/29/2015)

---

So I guess the table name is "elmah"?! It's somewhat confusing with all the different "table names" given.

DROP INDEX PK_ELMAH_Error ON elmah

DROP INDEX...

Thanks again Scott, but it's saying both indexes are not present or I don't have permission.

I did sp_changedbowner to my login and get the same result.

ScottPletcher (1/29/2015)

---

Drop all the indexes, starting with the nonclustered, then recreate them, starting with clustered. Unless the table itself is damaged, that's likely your best chance to clean this...