Does SonarQube provide supported tooling to reverse a committed database schema migration?
0 reputation · 15 Nov 2020, 06:22 UTC
I need to determine whether a committed SonarQube database schema migration can be reversed using supported tooling if an upgrade must be rolled back. The upgrade process applies forward schema changes automatically at startup and recommends a pre-upgrade database backup, but the available documentation does not state whether any command or administrative option can undo those changes after they are committed.
This assumes SonarQube 9.x or 10.x with an external database and no manual schema modifications. It is a design and operational question, not a report of a failed upgrade or an observed error.
Does SonarQube provide supported tooling to reverse a committed database schema migration? What conditions make a schema change irreversible? Is restoring the database from a pre-upgrade backup the only supported way to return to an earlier version after migration?