but how you came to know this is SQL 2000?I haven't worked on 2000...
Because it's posted in the SQL 2000 forum, because the error messages are in the SQL 2000 form (they were all rewritten for SQL 2005) and because the corruption message references sysobjects, a table that does not exist in SQL 2005+
It could be SQL 7 too, but it's definitely not SQL 2005 or higher.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass