Help-Corrupt table

This is just a followup if anybody's curious. This hotfix=20
didn't totally fix the error. DBCC CheckTable and CheckDB=20
were still giving errors. Exception_Access_Violations=20
were still occuring and the SQL server was actually=20
stopping itself. The hotfix did at least make it so that=20
I could at least select from the table and recreate it=20
without having to go to backup. So I just recreated the=20
table and dropped the old one. All is good now...
[vbcol=seagreen]
>--Original Message--
>Thanks, that was it. Had to get the hotfix and test it=20
>and all, but that was the problem.
>Thanks,
>Van
>return=20
>clustered=20
>when=20
>this=20
you=20[vbcol=seagreen]
>might=20
>BOL=20
and=20[vbcol=seagreen]
>in=20
mind,=20
>except=20
>same=20
>somehow. =20
>.
>
Thanks everyone for all your postigs. This is not the first time I meet
hypotetical clustered index, and they always screw up the tables they
are on. Most of the time they just hung select statement. Now it was
DBCC CHECKDB which was screwed. I was lucky enough that my hypotetical
friend index had typeable name and I managed to drop it. As soon as I
dropped it the message had gone.
Thanks!
Eugene
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!