Tag Info

New answers tagged

3

Have you tried REPAIR TABLE; or myisamchk --recover tbl_name http://dev.mysql.com/doc/refman/5.1/en/repair-table.html --EDIT-- As mentioned in the comments under your question, convert your tables to InnoDB tables which are transactional. This should help prevent corruptions in the future.


1

Msg 8928, Level 16, State 1, Line 1 Object ID 1326627769, index ID 1, partition ID 72057594048872448, alloc unit ID 72057594055557120 (type LOB data): Page (1:69965) There is corruption in your SQL Server database column is LOB and may have VRCHAR datatype. Index ID 1 indicated problem with Clustered index so I guess minimum repiar options repair ...


3

It continues to become suspect after. Please provide me the permanent solution. The permanent solution is to figure out WHY/WHAT is causing the database to go suspect. Is it a filter drivers, bad hardware, etc. We don't know and can't tell you, this is something you'll need to inspect on your own. You'll want to get your sysadmins involved as well. ...



Top 50 recent answers are included