How to check your database for corruption: Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

curprev 10:0310:03, 3 January 2012‎ Helen Foster talk contribs‎ 2,522 bytes −12‎ performance template

curprev 20:1220:12, 20 December 2010‎ chris collman talk contribs‎ 2,534 bytes +267‎ →‎MySQL: Give CHECK TABLE command for the weak of heart

curprev 08:5608:56, 3 March 2010‎ Mark Johnson talk contribs‎ 2,267 bytes −45‎ Removed flippant comment about MySQL not being a "proper" database. This isn't useful to someone looking for help with database corruption.

curprev 19:4519:45, 30 January 2010‎ Gisela Hillenbrand talk contribs‎ 2,312 bytes +58‎ No edit summary

curprev 01:3801:38, 16 January 2009‎ Tim Hunt talk contribs‎ 2,254 bytes −6‎ →‎MySQL
curprev 01:3701:37, 16 January 2009‎ Tim Hunt talk contribs‎ 2,260 bytes +2,260‎ New page: Database corruption usually occurs as a result of a hardware (especially disk-based) failure, or when a disk becomes full. Typical symptoms are failure on login, with this message displaye...

Documentation

How to check your database for corruption: Revision history

3 January 2012

20 December 2010

3 March 2010

30 January 2010

16 January 2009