Timeline for SQL Server mistaken update rows without backup
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2019 at 5:47 | comment | added | The Real Codeslinger |
@JohnEisbrener We have no backups. The database was in FULL recovery mode while the mistake was happened.
|
|
| Feb 18, 2019 at 15:16 | comment | added | John Eisbrener |
What backups do you have available? Was the database in SIMPLE recovery mode while running the bad UPDATE?
|
|
| Feb 18, 2019 at 11:13 | history | edited | The Real Codeslinger | CC BY-SA 4.0 |
added 291 characters in body
|
| Feb 18, 2019 at 9:22 | answer | added | John K. N. | timeline score: 3 | |
| Feb 18, 2019 at 8:27 | answer | added | Mr Zach | timeline score: 0 | |
| Feb 18, 2019 at 6:00 | comment | added | The Real Codeslinger | @Akina Then I think it's time to exit the office. Because the data was so important. At least I faced an awful experience which should not be repeat ever. | |
| Feb 18, 2019 at 5:50 | comment | added | Akina | No backup - no revert. The only way to restore some previous DB state is to restore backup before timepoint in question, then repeat transactions from backup time till this timepoint. Transaction log do not store what data was stored in a table before transaction and was altered/deleted by a transaction. You have no backup. So your data loss is now permanent. | |
| Feb 18, 2019 at 5:15 | review | First posts | |||
| Feb 18, 2019 at 7:34 | |||||
| Feb 18, 2019 at 5:11 | history | asked | The Real Codeslinger | CC BY-SA 4.0 |