Does everything happen in threes? It all started when I used an older version of procedure to perform a certain function. A silly but not uncommon error. What happened next was simply astounding.
To unrolled back my mistake, another application database need to have a few tables cleared out. Since I am not familiar with this application, I let my colleague to perform this task with the application owner. What can go wrong right?
They cleared out a wrong table. A table which I am told is very critical. The only way to solve this is to restore last night’s backup. Unrolling back the database transaction log was not advisable as it would end up at an unknown state.
The database restore process was interesting. The backup software refuse to restore to an alternate location on another database server. In the end we tried to restore the database offline with a different name.
Big mistake.
The restored database nuked the current database, that we trying hard to preserve. Subsequent investigation revealed that the restore problem was caused by the backup software client account configuration. Some thing that has been running for the past 2 years.
There are days were it is a good idea to stay in bed.