# Performing the post-upgrade steps

{% hint style="warning" %}
After an upgrade, some projects might be temporarily greyed out in the UI. This is because SonarQube is reindexing your projects, and they become available in the UI as they are reindexed. Note that you can already run analyses on these projects. See [reindexing](https://docs.sonarsource.com/sonarqube-server/10.5/instance-administration/reindexing "mention") for more information.
{% endhint %}

## Post-upgrade checklist <a href="#checklist" id="checklist"></a>

* Verify the version of the Sonar scanner: see **Verifying the installed Sonar scanner version on the scanner host**.
* For an Oracle database: clean up the database, see **Cleaning up the Oracle database**.
* For a PostgreSQL database: clean up the database, see **Cleaning up the PostgreSQL database**.
* For a Microsoft SQL database with Windows authentication: verify the JDBC driver version, see **Verifying the Microsoft SQL JDBC driver version**.
* If using an external configuration to control SonarQube Server (through a script or running as a service): update the service to point to the new installation directory, see **Updating a service to point to the new installation directory**.
* If SonarQube is running as a service on Linux with SystemD, then you must update the `sonarqube.service` file: see **Configuring SonarQube to run as a service**.
* If you are using the Web API, check at some point the usage of deprecated Web API endpoints and parameters: see [api-deprecation](https://docs.sonarsource.com/sonarqube-server/10.5/instance-administration/monitoring/api-deprecation "mention").

## Verifying the installed Sonar scanner version on the scanner host <a href="#verify-sonarscanner-version" id="verify-sonarscanner-version"></a>

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.

## Cleaning up the Oracle database <a href="#clean-up-oracle-db" id="clean-up-oracle-db"></a>

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 all\_unused\_col\_tabs.

## Cleaning up the PostgreSQL database <a href="#clean-up-postgresql" id="clean-up-postgresql"></a>

You can fix the table and index bloating by performing [vacuuming](https://www.postgresql.org/docs/16/routine-vacuuming.html#VACUUM-FOR-SPACE-RECOVERY) in order to reclaim unused disk space. In some specific cases, a [reindex](https://www.postgresql.org/docs/16/routine-reindex.html)is required afterward.

## Verifying the Microsoft SQL JDBC driver version <a href="#verify-jdbc-version" id="verify-jdbc-version"></a>

If you use Microsoft SQL Server with Windows Authentication, make sure that you’re using a supported version of the Microsoft SQL JDBC Driver package. The minimum supported version is the one mentioned on the [installing-the-database](https://docs.sonarsource.com/sonarqube-server/10.5/setup-and-upgrade/install-the-server/installing-the-database "mention") page.

## Updating a service to point to the new installation directory <a href="#update-external-service" id="update-external-service"></a>

If you use an external configuration, such as a script or Windows Service to control your server, you’ll need to update it to point to the new value of installation directory (\<newSonarQubeHome>).

For Linux it depends how you implemented the service.

For Windows, update your service by running the following commands:

```css-79elbk
sc delete SonarQube
<newSonarQubeHome>\bin\windows-x86-64\SonarService.bat install
```