I see a hypothetical index on the corrupt table=20
named "ĸ8=04". It's not really a lower case "k". It's=20
something else and the square is somekind a carrage return=20
or something because there is a blank line between this=20
index name and the next. This index is listed as a=20
clustered, hypothetical index. I already have a clustered=20
index on this table (different fields). Not sure if a=20
clustered hypothetical index is valid. And the name? I=20
tried to drop it. Said it didn't exist but left the=20
square out of the name (like it didn't see the square when=20
it tried to drop it. So I u used brackets to refference=20
it, and it says it's still not there (with the square this=20
time).
>--Original Message--
>In that case no - sorry, you will need to restore from=20
>backup.
>If you still have access to your Databases Data then you=20
>could re-create it using the generate SQL (but that might=20
>not work as it looks at the tables that caused the=20
error),=20
>DTS it, delete the old one, then rename the new one.
>BTW CHECKTABLE and CHECKDB are different if you check BOL=20
>under DBCC CHECKDB you will see 'DBCC CHECKDB performs=20
the=20
>same checking as if both a DBCC CHECKALLOC statement and=20
a=20
>DBCC CHECKTABLE statement were executed for each table in=20
>the database.'
>Anyway sorry I can't be of more help.
>Peter
>"Age is an issue of mind over matter. If you don't mind,=20
>it doesn't matter."=20
>Mark Twain=20
>
the=20[vbcol=seagreen]
restored=20[vbcol=seagreen]
>options=20
>without=20
>.
>That KB has nothing whatsoever do to with the problem described. CHECKDB
won't do anything different from CHECKTABLE in this case. You've got system
table corruption that DBCC repairs will not fix so you must restore from
your last known good backup. Tibor's link is a good set of steps to follow.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:068c01c51903$51607780$a601280a@.phx.gbl...
Hmm Interesting, this maybe of help.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;818097
Peter
"All generalizations are false, including this one."
Mark Twain
>--Original Message--
>I see a hypothetical index on the corrupt table
>named "ĸ8 ". It's not really a lower case "k". It's
>something else and the square is somekind a carrage
return
>or something because there is a blank line between this
>index name and the next. This index is listed as a
>clustered, hypothetical index. I already have a
clustered
>index on this table (different fields). Not sure if a
>clustered hypothetical index is valid. And the name? I
>tried to drop it. Said it didn't exist but left the
>square out of the name (like it didn't see the square
when
>it tried to drop it. So I u used brackets to refference
>it, and it says it's still not there (with the square
this
>time).
>
might[vbcol=seagreen]
>error),
BOL[vbcol=seagreen]
>the
>a
in[vbcol=seagreen]
except[vbcol=seagreen]
same[vbcol=seagreen]
>the
somehow.[vbcol=seagreen]
>restored
>.
>|||Oops - mistyped the URL and looked at the wrong KB article. Well done Peter.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:e4R1dHRGFHA.1292@.TK2MSFTNGP10.phx.gbl...
> That KB has nothing whatsoever do to with the problem described. CHECKDB
> won't do anything different from CHECKTABLE in this case. You've got
system
> table corruption that DBCC repairs will not fix so you must restore from
> your last known good backup. Tibor's link is a good set of steps to
follow.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
> news:068c01c51903$51607780$a601280a@.phx.gbl...
> Hmm Interesting, this maybe of help.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;818097
> Peter
> "All generalizations are false, including this one."
> Mark Twain
>
> return
> clustered
> when
> this
> might
> BOL
> in
> except
> same
> somehow.
>
Friday, March 9, 2012
Help-Corrupt table
Labels:
20something,
case,
corrupt,
database,
help-corrupt,
hypothetical,
index,
microsoft,
mysql,
oracle,
server,
sql,
table,
table20named
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment