Installing the Database
Several database engines are supported. Be sure to follow the requirements listed for your database, they are real requirements not recommendations.
Create an empty schema and a sonarqube user. Grant this sonarqube user permissions to create, update and delete objects for this schema.
Microsoft SQL Server
Note that collation MUST be case-sensitive (CS) and accent-sensitive (AS).
Note that READ_COMMITED_SNAPSHOT MUST be set on the SonarQube database.
MS SQL database's shared lock strategy may impact SonarQube runtime. Making sure that "is_read_committed_snapshot_on" is set to true prevents SonarQube facing potential deadlocks under heavy loads.
If you want to use integrated security, you have to download the Microsoft SQL JDBC Driver 6.2 package from https://www.microsoft.com/en-us/download/details.aspx?id=55539 and copy sqljdbc_auth.dll to any folder in your path. You have to copy the 32 bit or 64 bit version of the dll depending upon the architecture of your server machine. If you are running the SonarQube as a windows service and want to use Integrated security, please make sure the windows account under which the service is running has permission to connect your SQL Server. The account should have db_owner database role membership. Otherwise, if you are running the SonarQube server from a command prompt and want to use Integrated security, the user under which the command prompt is running should have db_owner database role membership. Also ensure that sonar.jdbc.username or sonar.jdbc.password properties are commented, otherwise SonarQube will use SQL Authentication.
If you want to use SQL Authentication, use the following connection string. Also ensure that sonar.jdbc.username and sonar.jdbc.password are set appropriately.
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:
Oracle driver versions 220.127.116.11 and 18.104.22.168 have major bugs, and are not recommended for use with the SonarQube ecosystem (see more details).
If you want to use a custom schema and not the default "public" one, the PostgreSQL
search_path property must be set:
MySQL (not recommended)
Data Center Edition
MySQL is not supported for Data Center Edition
There are two well-known engines that can be used in MySQL: MyISAM and InnoDB. MyISAM is the oldest of the two engines and is being progressively replaced by InnoDB. InnoDB is clearly faster and scales better with SonarQube as the number of projects under quality control increases. If you were an early adopter of SonarQube, you probably have a series of table that are still using MyISAM. To improve performances, you should change the engine for all tables to InnoDB.
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.
Installing the Web Server
Then download and unzip the distribution (do not unzip into a directory starting with a digit).
<install_directory> (below) refers to the path to the directory where the SonarQube distribution has been unzipped.
Setting the access to the Database
Edit <install_directory>/conf/sonar.properties to configure the database settings. Templates are available for every supported database. Just uncomment and configure the template you need and comment out the lines dedicated to H2:
Adding the JDBC Driver
Drivers for the supported databases (except Oracle) are already provided. Do not replace the provided drivers; they are the only ones supported.
For Oracle, copy the JDBC driver into <install_directory>/extensions/jdbc-driver/oracle.
Configuring the Elasticsearch storage path
By default, Elasticsearch data is stored in <install_directory>/data, but this is not recommended for production instances. Instead, you should store this data elsewhere, ideally in a dedicated volume with fast I/O. Beyond maintaining acceptable performance, doing so will also ease the upgrade of SonarQube.
Edit <install_directory>/conf/sonar.properties to configure the following settings:
The user used to launch SonarQube must have read and write access to those directories.
Starting the Web Server
The default port is "9000" and the context path is "/". These values can be changed in <install_directory>/conf/sonar.properties:
Execute the following script to start the server:
- On Linux/Mac OS: bin/<YOUR OS>/sonar.sh start
- On Windows: bin/windows-x86-XX/StartSonar.bat
You can now browse SonarQube at System administrator credentials are admin/admin).(the default
Tuning the Web Server
By default, SonarQube is configured to run on any computer with a simple Java JRE.
For better performance, the first thing to do when installing a production instance is to use a Java JDK and activate the server mode by uncommenting/setting the following line in <install_directory>/conf/sonar.properties:
To change the Java JVM used by SonarQube, simply edit <install_directory>/conf/wrapper.conf and update the following line:
Advanced Installation Features
Grant more memory to the web server / compute engine / elastic search
To grant more memory to a server-side process, uncomment and edit the relevant
javaOpts property in $SONARQUBE_HOME/conf/sonar.properties, specifically:
sonar.web.javaOpts(minimum values: -server -Xmx768m)
Cannot connect to MySQL database
By default, remote access to MySQL database server is disabled for security reasons. If you want to remotely access the database server, you need to follow this quick guide.
Failed to start on Windows Vista
SonarQube seems unable to start when installed under the Program Files directory on Windows Vista. It should therefore not be installed there.
Failed to start SonarQube with Oracle due to bad USERS table structure
When another(s) USERS table exists in the Oracle DB, if the sonarqube user has read access on this other USERS table, the SonarQube web server can't start and an exception like the following one is thrown:
To fix this issue, the rights of the sonarqube Oracle user must be decreased to remove read access on the other USERS table(s).
Failed to connect to the Update Center via proxy
Double check that settings for proxy in file SONARQUBE_HOME/conf/sonar.properties are correctly set.
Note that if your proxy username contains "\" (backslash), then it should be escaped - for example username "domain\user" in file should look like:
For some proxies, exception "java.net.ProtocolException: Server redirected too many times" might mean an incorrect username or password has been configured.