Timeline for DBCC CHECKDB - SQL Log Says Completed, SQL Server Agent Says Failed
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2019 at 19:10 | history | edited | sepupic | CC BY-SA 4.0 |
added 952 characters in body
|
| Jan 29, 2019 at 18:49 | comment | added | sepupic | Ok, even if it's the same server, your dbcc checkdb failed on 25/01, this is the first message produced by CHECKDB(the command issued on 25/01), but this db was OVERWRITTEN with the copy of CellTestData, and when this restored copy went online, it reported that checkdb on CellTestData was finished without errors on 24/01, it's NOT checkdb that produced this message, it was the server that read this in the db restored. It just reported WHAT WAS WRITTEN in CellTestData when bringing db online. I'll try to update my answer to be more clear | |
| Jan 29, 2019 at 15:30 | comment | added | A Sch | I'm not sure I follow, as I only have a single server that these DBs are running on. [CellTestData_QC] is a nightly restore of [CellTestData]. | |
| Jan 28, 2019 at 8:30 | history | answered | sepupic | CC BY-SA 4.0 |