Check out DBCC CHECKTABLE() in the BOL.

-Mike

>I have a table with 20+ fields. I can query the table by itself on any field without any problems, but if I try to create a query on the cardassigned field (int) and link it to another table based on cardassigned then the SQL Server's CPU shoots up to 100 percent and it is basicly locked. I can run a selecting just that field and it works great, I can even put a filter on that field in the where clause and it still works. That table (meetproc) only has 18000 records, but I thought maybe I needed an index on that field. So, in enterprise manager, I went an added an index on cardassigned. As soon as I clicked the apply button, the CPU on the sql server shot up to 100% and stayed their until I killed the enterprise manager on my other workstation (15 minutes later). The field is an int and there are no null values. Below is the simple query I found the problem with.
>
>

>SELECT dbo.meetproc.cardassigned
>FROM   dbo.meetproc INNER JOIN
>       dbo.cosuper ON dbo.meetproc.cardassigned = dbo.cosuper.cosuperid
>

>
>Are there any database procedures I can run to veryify the field/table? Any clues to what I need to check greatly appreciated.
>
>Kirk