Database Changes: Roll Back or Fix Forward?
![](https://cdn.prod.website-files.com/65c3a844357606c1b08a1e98/65c64e0db76ed0f6749815f3_Fatabase%20changes%20roll%20back%20or%20fix...jpg)
Details
How many times has your team had to roll back a database change from production in the last two weeks? If your answer is greater than zero, there might be a problem.
Database rollback functionality is important. It’s like having a fire extinguisher in your kitchen. You’re a responsible person for having it in case of emergencies. However, if you have fires in your kitchen over and over again, it’s a problem and you probably should look into prevention as well as having an emergency plan. An ounce of prevention is worth a pound of cure, after all.
Covered in this white paper
- Most common approaches to database issues
- Benefits of fixing forward
- When it still makes sense to roll back
- What role automation plays in the debate
- Best practices for database DevOps