The only prerequisite for running SonarQube is to have Java (Oracle JRE 8 onwards or OpenJDK 8 onwards) installed on your machine.
Note: On Mac OS X it is highly recommended to install Oracle JDK 8 (or higher) instead of the corresponding Oracle JRE since the JRE installation does not fully set up your Java environment properly. See this post for more information.
- The SonarQube server requires at least 2GB of RAM to run efficiently and 1GB of free RAM for the OS.
- The amount of disk space you need will depend on how much code you analyze with SonarQube. As an example, SonarQube.com the public instance of SonarQube, has more than 25 millions lines of code under analysis with 4 years of history. SonarQube.com is currently running on a Amazon EC2 c3.large instance, using about 10 Gb of drive space. It handles 320+ projects having roughly 3M open issues. SonarQube.com is running on PostgreSQL 9.5 and it is using about 15Gb of drive space.
- SonarQube must be installed on hard drives that have excellent read & write performance. Most importantly, the "data" folder houses the Elasticsearch indices on which a huge amount of I/O will be done when the server is up and running. Great read & write hard drive performance will therefore have a great impact on the overall SonarQube server performance.
|The SonarQube Java analyser is able to analyse any kind of Java source files regardless of the version of Java they comply to. But SonarQube analysis and the SonarQube Server require specific versions of the JVM.|
2008 (MSSQL Server 10.0) with bundled Microsoft JDBC driver. Express Edition is supported. Support will end with SonarQube 6.1 (
End of support of MSSQL 2008
Collation must be case-sensitive (CS) and accent-sensitive (AS) (example: Latin1_General_CS_AS)
Both Windows authentication (“Integrated Security”) and SQL Server authentication are supported. See the Microsoft SQL Server section in Installing page for instructions on configuring authentication.
5.6 is supported since SonarQube 3.5
Must be configured to use UTF8 charset and a case-sensitive (CS) collation
Only InnoDB storage engine is supported, but not MyISAM
10G (not supported since 5.0)
Must be configured to use a UTF8 charset and BINARY sort
The driver ojdbc14.jar is not supported
Must be configured to use UTF8 charset
Microsoft Internet Explorer