Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once all SonarQube tables are using the InnoDB engine, the first thing to do is allocate a maximum amount of RAM to your MySQL instance with the innodb_buffer_pool_size parameter and give at least 15Mb to the query_cache_size parameter. Read this article about InnoDB Performance Optimization Basics for more information.

Oracle

When having two SonarQube schemas on the same Oracle instance, especially if they are of two different versions, SonarQube gets confused and picks the first it finds. To fix this issue:

  • Either privileges associated to the SonarQube Oracle users should be decreased
  • Or a trigger should be defined on Oracle side to automatically alter the SonarQube Oracle user session when establishing a new connection:
     
Code Block
languagetext
ALTER SESSION SET current_schema="MY_SONARQUBE_SCHEMA"

PostgreSQL

If you want to use a custom schema and not the default "public" one, the PostgreSQL search_path property must be set:

Code Block
languagetext
ALTER USER mySonarUser SET search_path to mySonarQubeSchema

Anchor
installingWebServer
installingWebServer
Installing the Web Server

...