We are planning to upgrade our SonarQube instance from version 2025.1.4 to 2026.1.0. Since the upgrade from 9.9.9 to 2025.1.4 involved database schema changes, we would like to confirm whether the transition from 2025.1.4 to 2026.1.0 also includes any database schema updates or if the schema remains unchanged.
In all likelihood, yes. They’re not huge or blocking like some upgrades, but you do need to run /setup to update the database after upgrading the instance. And the logs of that process I saw indicated it was making changes to my database, not just checking it.
Also, a number of features have been added since 2025.1.x, such as Sandbox in 2025.5, so I’d expect new objects for that.
In my upgrade last week I didn’t have any issues, but I’d still take a backup of the DB prior to upgrading. Databases of new versions of SonarQube are almost never reverse-compatible if that’s what you’re curious about. SonarQube explicitly includes database rollback as a part of reverting to a previous version, so it’s safer to assume updates make a database incompatible with prior versions.
1 Like
Hello,
I can confirm that upgrading from 2025.1.4 to 2026.1.0 definitely means schema changes; e.g., support for Advanced Security in 2025.4.0, sandboxing in 2025.6.0.
To William’s point, please always take a backup of the DB prior to any upgrade.
We also discuss per DB-vendor maintenance steps – I cannot emphasize how important these are to ensure that your DB continues to perform as well as it should.
Best regards,
Wayne
1 Like
Thanks @wmarshall and @wayne.khan for the confirmation .
But SonarQube typically documents any database schema changes in their release or upgrade notes, just as they did for earlier versions where schema updates were required. For version 2026.1.x, there is no mention of any database schema changes or instructions on how to handle them during the upgrade.
Hello @rahul.phatkare,
But SonarQube typically documents any database schema changes in their release or upgrade notes, just as they did for earlier versions where schema updates were required.
I’m not sure that we do do this. Can you link me up to an example? If it is something we do do, and it’s missing for whatever reason, I’m happy to get our Documentation squad to put it in.
… how to handle them during the upgrade.
There is nothing to handle once you navigate to /setup and click through the UI – the system will apply schema changes automatically.
Best regards,
Wayne
1 Like
For 2025.1. version there was video on release notes page .PFB screeenshot but currently unfortunately I am not able to access it as your team had made it private .But because of that we got to know about the DB schema change which was happend in 2025.1.* version and also got to know about how to do db migration during upgrade process.But now this links are not working ,any reason to remove them from documents ?
Your team should also inform us in advance whenever a database schema change is expected in any upcoming SonarQube release. This will help us prepare properly, minimize the risk of unexpected failures during upgrades, and ensure we can safely roll back to the previous version if necessary.
Hello Rahul,
I remember that video. But the focus there was more to provide upgrade guidance than anything.
To your point about safety, just always backup the DB so roll back becomes possible.
Best regards,
Wayne
Hello Rahul,
I was reminded that have an SonarQube Server LTA Update Hub that my colleagues keep well-updated, including a new version of the “Ace your update” video. (Search for this phrase, or simply scroll down a bit.)
Best regards,
Wayne
documentation related to any version upgrade should kept at one place like here where release notes/upgrade notes are present.