This nice article tells me SQL Server can automatically repair a page and we have an event where we think it did repair a page, literally we got notices early Sunday morning while we were all attending church and by the time I could log in the database that caused the error passed a DBCC check. So I was digging through the SQL Server error logs to verify but I cannot find anything other than the 3 error log entries at the bottom, but if you look at the 9:52 one it looks like this is when the automated repair was completed. Again, all I want to do is find some place that says an Automated Page Repair did happen?
http://technet.microsoft.com/en-us/library/bb677167(v=sql.105).aspx
| 5/5/2013 9:52 | spid316 | Unknown | A read of the file 'G:\ExigoData\Stemtech.mdf' at offset 0x00004316548000 succeeded after failing 4 time(s) with error: incorrect pageid (expected 1:35173028; actual 0:0). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online. |
| 5/5/2013 9:38 | spid132 | Unknown | SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:35173028; actual 0:0). It occurred during a read of page (1:35173028) in database ID 21 at offset 0x00004316548000 in file 'G:\ExigoData\Stemtech.mdf'. 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<c/> see SQL Server Books Online. |
| 5/5/2013 9:38 | spid132 | Unknown | Error: 824<c/> Severity: 24<c/> State: 2. |