This version of the SonarQube documentation is no longer maintained. It relates to a version of SonarQube that is not active.

See latest version
Start Free
10.1 | Analyzing source code | Languages | PL/SQL

PL/SQL

On this page

PL/SQL analysis is available starting in Developer Edition.

Language-specific Properties

Discover and update the PL/SQL-specific properties in Administration > General Settings > Languages  > PL/SQL.

Advanced parameters

Default schema

ParameterDescription
sonar.plsql.defaultSchemaWhen a schema object (table, view, index, synonym) is referenced in SQL code without a schema prefix, the analyzer will assume that it belongs to this schema.

Data dictionary

Some rules raise issues only when a data dictionary is provided during analysis. To provide a data dictionary, you must define the following properties in the sonar-project.properties file or on the scanner command line using the -D prefix:

ParameterDescription
sonar.plsql.jdbc.urlURL of the JDBC connection. Required for data dictionary lookup. For example: jdbc:oracle:thin:@my-oracle-server:1521/my-db
sonar.plsql.jdbc.userJDBC user to authenticate the connection.
sonar.plsql.jdbc.passwordJDBC password provided to authenticate the connection.
sonar.plsql.jdbc.driver.pathPath or URL of the Oracle JDBC driver JAR.
sonar.plsql.jdbc.driver.classJava class name of the Oracle Driver. For example: oracle.jdbc.OracleDriver

Providing this configuration allows SonarPLSQL to query data dictionary views such as SYS.ALL_TAB_COLUMNS in order to better analyze your SQL.


Was this page helpful?

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARLINT, SONARQUBE, SONARCLOUD, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Creative Commons License