bad idea. bad bad.
first, don't do anything like take the database offline or anything without expert advice; Gail Shaw monitors this forum frequently..
run DBCC CHECKDB('db name') WITH NO_INFOMSGS, ALL_ERRORMSGS and post the results here.
with that, we can tell you a lot more.
you might be able to do anything from page level restore to get the data back, maybe migrate the data out to a new table to fix it, and many other possibilities.there's just too many possibilities without .
letting ANYTHING other than SQL server touch the bits and bytes of the data will guarantee corruption and loss of data.
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!