Databases in Suspect Mode

Bodhi108
Bodhi108 used Ask the Experts™
on
Today, someone added space to one of our disks where our log files reside.  The drive was backed up without the databases being stopped!  Before restoring the drive, the database was stopped.  Luckily, no new data to the database had been added since we did the backup.

When we brought up the databases, they all became suspect.  Luckily, I had a backup of two of the databases but the other two, the ReportServer and ReportServerTempTempDB, we have never done a backups!!!

I believe the reason it is suspect is because our log files are out of sync.  Our .mdf should be fine but the .ldf is not.  Is there a way I can bring the database out of suspect?

Thanks!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
NEED HELP on this ASAP!  This is production if you can believe it!

Thanks so much!
Commented:
Found the anwer on StackOverflow which says it found the answer on Experts-Exchange!  I looked but I didn't give it thorough look!  So THANK YOU for whoever posted this!  YES!
6. ALTER DATABASE yourdb SET EMERGENCY
7. ALTER DATABASE yourdb SET SINGLE_USER
8. DBCC CHECKDB (yourdb, REPAIR_ALLOW_DATA_LOSS)
9. ALTER DATABASE yourdb SET MULTI_USER
10. ALTER DATABASE yourdb SET ONLINE

Commented:
<<The drive was backed up without the databases being stopped! >>
A disk backup is not a good way to backup live databases as you noticed now. The sql backup is there for to see it is usable.

Don't forget to change your backup-strategy that any new database will automaticly be in your backup-job.

Author

Commented:
Found answer by googling but it gave credit to finding the answer on experts-exchange.  Followed steps and it corrected the suspect databases.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial