bear
02-03-2003, 06:04 AM
A message brought to those of you that have been a bit overworked lately (like myself):
I tried upgrading my install, but since I'd been running 9.2.2, I couldn't (wanted 9.3). So, I tried a new install, which needed to have an empty database. I drop the tables and proceed...it complains the tables and rows still exist.
Uh-oh.
Sure enough, I'd dropped the wrong database! Serves me right for doing this before I'm fully awake. Restored from backup, dropped the *right* tables, and all went perfectly well.
Moral of the story?
- Automatic, frequent sql backups are a *very* good idea.
- Coffee is to be administered *prior* to database work.
- Look twice before executing *anything* on the server...
I tried upgrading my install, but since I'd been running 9.2.2, I couldn't (wanted 9.3). So, I tried a new install, which needed to have an empty database. I drop the tables and proceed...it complains the tables and rows still exist.
Uh-oh.
Sure enough, I'd dropped the wrong database! Serves me right for doing this before I'm fully awake. Restored from backup, dropped the *right* tables, and all went perfectly well.
Moral of the story?
- Automatic, frequent sql backups are a *very* good idea.
- Coffee is to be administered *prior* to database work.
- Look twice before executing *anything* on the server...