Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Occasionally we have an issue where a record's previous data might get wiped while editing.

We backup our database every night for issues like this, however sometimes I am not available to do a restore immediately.

I've been asked to create a tool our editors can use to restore a record from a previous backup file.

I imagine this would look a lot like the a Webmin panel, which leads me to believe I may be reinventing the wheel. However, our editors find Webmin difficult to work with, so this isn't a solution for us.

Is anyone familiar with something we can use for the purpose of restoring a single record?

If not, are there any best practices I should abide by?

share|improve this question
up vote 0 down vote accepted

Restore is overkill.

I'd use history/change tracking within the database/application itselF: then "rollback" becomes a standard day to day business or support actions

This would be with history tables, or Slowly Changing Dimension type 2 tables, to store "old" versions of rows. Perhaps with some schedules clean-up to purge older versions

share|improve this answer
Thanks. So I would be able to use a trigger to track with the history table? – Yazmin Mar 6 '12 at 3:10
@Yazmin: yes, this is the easiest way – gbn Mar 6 '12 at 7:37
Thanks. I'll look into that then. – Yazmin Mar 6 '12 at 14:29

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.