database (suspect) | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

database (suspect)

Hi .. northwind database in my server shows suspect.. I checked the error log for information.. error:823 severity:24 state:6
I/O error 23 ( Data error ( Cyclic redundancy check)) detected during read at offset
0000000000000000 in file ‘D:program FilesMicrosoft SQL ServerMSSQLdata
orthwnd.ldf’.. Device activation error.The physical file name ‘D:program FilesMicrosoft SQL ServerMSSQLdata
orthwnd.ldf’.. may be incorrect… What are the possible ways so that the suspect flag will be removed.?
krishna chaitanya.s
project engineer-SQLDBA

Check the location ‘D:program FilesMicrosoft SQL ServerMSSQLdata’ whether both the files .MDF / .LDF is there or not. Also check whether your drive have enough space for the growing database. Use sp_resetstatus to change the status of your db. HTH
Surendra Kalekar
Hi,<br />please read below thread to recover from Suspect Database <br /><br /<a target="_blank" href=http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=9411>http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=9411</a><br /><br /><br />[<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ />]<br />HTH<br />Regards<br /><br /><br />Hemantgiri S. Goswami<br />[email protected]<br />"Humans don’t have Caliber to PASS TIME , Time it self Pass or Fail Humans" – by Hemantgiri S. Goswami<br />
Hi surendra ,
i checked what u said …the files are present….disk space is also there…
I run the sp_resetstatus and restart the sql server services…..but it didn’t work.. Hi hemant….i refer the article ….it’s nice.. Finally i restore the database from backups….. i want to find why the CRC ( Cyclic redundancy check ) error came? any thoughts?
krishna chaitanya.s
project engineer-SQLDBA

CRC error refers to the disk related and make sure hardware is not compromised here, run DBCC CHECKDB and fix any allocation errors. By all means it looks like there is a problem with the disk subsystem, take help of system admin to prevent the issues in future. It could be the issue of a corrupt block on the disk, so you need to check and use DBCC CHECKDB to fix the tables inconsistency. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>