Ctrlk
Start Free
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Pre-update steps

The pre-update steps you must perform before you start updating SonarQube Server.

Before you start

Consider the following before starting your upgdate:

  • SonarQube Server releases come with specific recommendations for updating from the previous versions. You should first read the Update notes for each version between your current version and the target version.

  • Database disk usage recommendations: During your update, tables may be duplicated to speed up the migration process. This could cause your database disk usage to temporarily increase to as much as double the normal usage. Because of this, we recommend that your database disk usage is below 50% before starting a migration.

Backup the database

First, we strongly recommend creating a backup of your database. A backup dump of the database creates a safety net should anything go wrong during the update process. It also allows for testing the update on a testing instance. See Testing the update section below for details.

Recommended database maintenance steps

For large instances, it can be helpful to perform database maintenance tasks like vacuuming, reindexing, and collecting statistics to ensure a smooth and efficient migration. These steps help eliminate table and index bloat, reclaim disk space, and optimize query performance, preventing unnecessary slowdowns during the update process.

Additionally, gathering fresh statistics ensures that the database query planner can make optimal execution choices. Neglecting these optimizations can lead to longer update times, increased disk usage, and potential indexing issues, affecting responsiveness after the migration.

The following commands will lock your database tables so they should be performed during the downtime window. The best effect will be achieved when they are run one after another.

PostgreSQL

VACUUM FULL
REINDEX DATABASE <db>
ANALYZE

Oracle

Microsoft SQL Server

SonarScanner compatibility

Check the minimum required SonarScanner version for the SonarQube Server version that you are updating to. See SonarScanners General requirements and individual scanner pages for more details.

SonarScanner
2026.3
2026.2
2026.1 LTA
2025.4 LTA
2025.1 LTA
9.9 LTA

SonarScanner CLI

8.0.1

8.0.1

8.0.1

7.2

7.0.1

4.8

Azure DevOp extension

8.2.0

8.1.0

8.0.1

7.3

7.1.1

5.11.1

Jenkins extension

2.18

2.18

2.18

2.18

2.17.3

2.15

SonarScanner for Maven

5.6.0.6792

5.5.0.6356

5.5.0.6356

5.1.0.4751

5.0.0.4389

3.9.1.2184

SonarScanner for Gradle

7.3.0.8198

7.2.3.7755

7.2.2.6593

6.2.0.5505

6.0.1.5171

3.5.0.2730

SonarScanner for .NET

11.2.0.135473

11.2.0.135473

11.0.0.126294

10.3.0.120579

9.0.2

5.11

SonarScanner for NPM

4.3.6

4.3.5

4.3.0

4.3.0

4.2.6

3.7.0

SonarScanner for Python

1.4.0.4676

1.3.0.4086

1.3.0.4086

1.1.0.2035

0.2.0.520

N/A

Testing the update

We recommend testing your update to:

  • Make sure your infrastructure can run the update and the new version of SonarQube.

  • Get an idea of how long the update will take.

  • Gain a better understanding of the update process and anticipate what you’ll need to do when performing the actual update.

To test your update:

  1. Create a staging environment using a recent backup of your production database. Your staging environment should be as similar to your production instance as possible because the resources and time needed to update depend on what’s stored in your database.

  2. Use this staging environment to test the update.

  3. Observe how long it takes to back up and restore systems and complete the process.

Related pages

PreviousDetermining the update pathNextPerforming the update

Was this helpful?