Upgrade the Server
Upgrading across multiple, non-LTS versions is handled automatically. However, if you have an LTS version in your migration path, you must first migrate to this LTS and then migrate to your target version.
Example 1 : 5.1 -> 7.0, migration path is 5.1 -> 5.6.7 LTS -> 6.7.x LTS -> 7.0 Example 2 : 6.2 -> 6.7, migration path is 6.2 -> 6.7.x LTS (where x is the latest patch available for 6.7 - you don't need to install all the intermediary patches, just take the latest)
This is a generic upgrade guide. Carefully read the Release Upgrade Notes of your target version and of any intermediate version(s).
Planning to Upgrade to a Commercial Edition? If you are moving to 6.7 LTS and installing a Commercial Edition, please read this documentation.
Before you start, back up your SonarQube Database. Upgrade problems are rare, but you'll want the backup if anything does happen.
- Download and unzip the SonarQube distribution of your edition in a fresh directory, let's say
- Manually install the non-default plugins that are compatible with your version of SonarQube. Use the Compatibility Matrix to ensure that the versions you install are compatible with your server version. Note that the most recent versions of all SonarSource code analyzers available in your edition are installed by default. Simply copying plugins from the old server to the new is not recommended; incompatible or duplicate plugins could cause startup errors.
- Update the contents of
$NEW_SONARQUBE_HOME/conf) with the settings of the related files in the
$OLD_SONARQUBE_HOME/confdirectory (web server URL, database, ldap settings, etc.). Do not copy-paste the old files. If you are using the Oracle DB, copy its JDBC driver into
- Stop your old SonarQube Server
- Start your new SonarQube Server
- Browse to
http://yourSonarQubeServerURL/setupand follow the setup instructions
- Reanalyze your projects to get fresh data
MySQL Deprecation and Migration
Starting with version 7.9, SonarQube will no longer support MySQL. To migrate from MySQL to a supported database, see the MySQL Migrator tool.
Starting with version 6.6, there's an additional step you may want to perform if you're using Oracle. On Oracle, the database columns to be dropped are now marked as UNUSED and are not physically dropped anymore. To reclaim disk space, Oracle administrators must drop these unused columns manually. The SQL request is
ALTER TABLE foo DROP UNUSED COLUMNS. The relevant tables are listed in the system table
Additional Database Maintenance
Refreshing your database's statistics and rebuilding your database's indices are recommended once the technical upgrade is done (just before the very last step).
For PostgreSQL, that means executing
VACUUM FULL. According to the PostgreSQL documentation:
In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done.
When upgrading SonarQube, you should also make sure you’re using the latest versions of the SonarQube scanners to take advantage of features and fixes on the scanner side. Please check the documentation pages of the Scanners you use for the most recent version compatible with SonarQube and your build tools.
SonarQube as a Linux or Windows Service
If you use external configuration, such as a script or Windows Service to control your server, you'll need to update it to point to
In case you used the InstallNTService.bat to install SonarQube as a Windows Service, run the $OLDSONARQUBEHOME/bin/.../UninstallNTService.bat before running the InstallNTService.bat of the $NEWSONARQUBEHOME.
Release Upgrade Notes
Usually SonarQube releases come with some specific recommendations for upgrading from the previous version. You should read the upgrade notes for each version between your current version and the target version.