WolfgangE (1/7/2013)
Maybe - and I really mean MAYBE - you can solve the problem by rebuilding the indexe mentioned in the error message.
Dropping and recreating should solve this particular corruption.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability