Sorry, Mike, I misunderstood your posting.

I believe that DBCC is kind of randomly spitting out errors. The "CHECKDB..." errors being displayed for the table that has 0 rows are some examples of this. Dropping/recreating the table with 0 rows made no difference.

I did try running dbreindex on 2 of the larger tables, thinking they would be more prone to errors. The error now is:

Server: Msg 823, Level 24, State 2, Line 1

I/O error (torn page) detected during read at offset 0x0000022e3d0000 in file 'K:\smsdw_fg_files\SMSPHdss800r_smsdre_data_fg07_1.ndf'.

What is a "torn page"? and how can it be corrected? Do I stand to lose some data here?