Database in Suspended Mode

Question

Hi,
I faced this problem suddenly when i was trying some indexes on a local dummy table(using 'sa' user id) on DB COSMOS. After working around indexes i saved the file and closed Query Analyzer. On relogging again with 'sa' user Id i faced the following problem "A connection was successfully established but then an error occured during the login process.(provider : Shared Memory Provider, error:0 - No process is on the other end of the pipe.) "
Then i logged in with Windows Authentication account. however i couldnt access DB COSMOS as it was put in Suspended Mode. On checking the event viewer i found below error
"SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xb42e9a1f; actual: 0xb45a9f73). It occurred during a read of page (2:0) in database ID 7 at offset 0000000000000000 in file 'E:\COSMIC\COSMOS_log.ldf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online."
Well how the above error can be repaired. There are no backups of this db. I cannot run DBCC CHECKDB command for COSMOS as the same has been suspended.
Please give me the solution to above problem.
Thanks

Answer 1

Hi ,
Thanks for the info. Lekss thanks for that article..it was quite useful.
Please check the below error that i found in error log.
2009-12-29 21:09:45.81 spid20s     Error: 824, Severity: 24, State: 2.
2009-12-29 21:09:45.81 spid20s     SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xb42e9a1f; actual: 0xb45a9f73). It occurred during a read of page (2:0) in database ID 7 at offset 0000000000000000 in file 'E:\COSMIC\COSMOS_log.ldf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2009-12-29 21:09:45.81 spid20s     Error: 3414, Severity: 21, State: 2.
2009-12-29 21:09:45.81 spid20s     An error occurred during recovery, preventing the database 'COSMOS' (database ID 7) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2009-12-29 21:09:45.85 spid53      EMERGENCY MODE DBCC CHECKDB (COSMOS, repair_allow_data_loss) WITH no_infomsgs executed by HOME\ADMIN terminated abnormally due to error state 5. Elapsed time: 0 hours 0 minutes 1 seconds.
by putting my DB in emergency mode i could get the tables.Luckily there were only ten tables. however how do i take backup of the entire database in this case. As mentioned above, on executing DBCC CheckDB ('DBname', REPAIR_ALLOW_DATA_LOSS) after setting dB to single User mode, the system still displayed that the dB was in suspect mode and cannot be opened. Also the other system dbs including master is damaged and in Online mode. how do i get damaged free dBs. What should be done in real live situation where data is very important.