Bear in mind there may still be transactional inconsistencies (where part of a transaction completed only), you could have orphaned rows (foreign key constraints that are now violated)
You need to check for stuff like that, but it needs knowledge of how the system works and what the data means.
Also run CheckConstraints, run a checkDB (without repair) and make sure that they don't pick any other problems up
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