Rollback: two ways back from a bad change (4/7)
Get Started
Two ways to roll back (4/7)
Most of governance is about stopping bad changes. Some get through anyway — reviewed, approved, valid, and still wrong. What matters at that point is how fast you can put things back.
Bytebase answers that two ways, depending on how the change went wrong:
DML rollback
A valid UPDATE with the wrong WHERE. Turn on Prior Backup and Bytebase saves the affected rows before the statement runs; afterwards, a Rollback link generates the SQL to put them back. Works for UPDATE and DELETE, across several databases at once.
DDL rollback
Every applied change saves a snapshot of the schema. Select Rollback on that entry and Bytebase generates the DDL to return the database to the earlier snapshot — on MySQL, PostgreSQL, Oracle, SQL Server, and more.
Neither one skips the process. Bytebase only prepares the rollback SQL; you review it and decide when to run it, just like any other change. The fix goes through the same review and leaves the same audit trail.
Bytebase — the standard for database governance.
