I have a really weird situation. I have a database with one table with torn pages, but the database is not suspect. The table is not in use (I think someone was doing some temp work and broke something) I cant BCP out the table. DBCC shows that this is the only object affected. Can I simply drop the table or will I risk the entire DB going suspect by so doing? its a 2tb db, and I haven't tried dropping a "bad" table before. I really don't want this to go suspect. We run weekly DBCC Checks and that's what picked up this table error. We cant go back to backups to an entire week, its out of the question, and worst case scenario, we migrate every table in the DB except for this one bad one and fix it that way, or run DBCC repair allow data loss. The Users want to avoid any outage if at all possible.

My thinking is, when dropping a table, doesn't that just affect the sysobjects/sysindexes tables, and return all the deleted pages back to the DB without scanning the table data? will this fix corruption in a single table or cause More damage? We can still read the table as long as we don't encounter one of the torn pages.