- Nobody wants backup but everyone cries for recovery
- Create your DB with foreign key references, because you should:
- make it as hard as possible for yourself to update/delete data and destroying the structural integrity / something else with that
- If possible, run on a system where you have to commit the changes before you permanently store them (i.e. deactivate autocommit while repairing the db)
- Try to identify your problem's classes so that you get an understanding how to fix without trouble
- Get a routine in playing backups into a database, always have a second database on a test server at hand so you can just work on that
- Because remember: If something fails totally, you need to be up and running again as fast as any possible
Well, that's about all I can think of now. Take the bold passages and you see whats #1 for me. ;-)
