http://www.devx.com/vb2themax/Tip/18624 ---------------------------------------- Contributing Editor, Writer & Forums Moderator http://www.SQL-Server-Performance.Com Visit my Blog at http://dineshasanka.spaces.live.com/
There is more information available on SQL Server books online about how can you recover from a suspect database, KBAhttp://support.microsoft.com/kb/889266 too. Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Hi, Added to what Satya has referred, I would suggest to read below articlehttp://www.myitforum.com/articles/18/view.asp?id=7381 Hemantgiri S. Goswami MS SQL Server MVP ------------------------- "Humans don't have Caliber to PASS TIME , Time it self Pass or Fail Humans" - by Hemantgiri S. Goswami http://hemantgirisgoswami.blogspot.com
If you have the db backup, then its better to detach the db and restore the db using the available backup. It will work fine. Sagar
... before that it is better to see why this database is getting suspect state, such as hardware issues or any corrupted page! Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Hi, Try this it will work.EXEC sp_resetstatus 'Yourdatabasename'ALTER DATABASE Yourdatabasename SET EMERGENCYDBCC checkdb(' Yourdatabasename ')ALTER DATABASE Yourdatabasename SET SINGLE_USER WITH ROLLBACK IMMEDIATEDBCC CheckDB (' Yourdatabasename ', REPAIR_ALLOW_DATA_LOSS) ALTER DATABASE Yourdatabasename SET MULTI_USER bye John