Skip to end of metadata
Go to start of metadata

Since SonarPLSQL 3.2, some rules raise issues only when a data dictionary is provided during the SonarQube 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:

JDBC Connection for the Data Dictionary

Property nameDescriptionRequiredFor Example
sonar.plsql.jdbc.url

JDBC URL
URL of the JDBC connection.

Yesjdbc:oracle:thin:@my-oracle-server:1521/my-db
sonar.plsql.jdbc.userJDBC User
JDBC user provided to authenticate the connection.
NoSonarPLSQL
sonar.plsql.jdbc.passwordJDBC Password
JDBC password provided to authenticate the connection.
No**************
sonar.plsql.jdbc.driver.pathJDBC Driver Path
Path or URL of the Oracle jdbc driver jar.
Nolib/ojdbc8-12.2.0.1.0.jar
sonar.plsql.jdbc.driver.classJDBC Driver Class
Java class name of the Oracle Driver.
Nooracle.jdbc.OracleDriver

Based on such a configuration, SonarPLSQL queries data dictionary views such as SYS.ALL_TAB_COLUMNS.

Schema

Property nameDescriptionRequiredFor Example
sonar.plsql.defaultSchema

Default Schema
When a schema object (table, view, index, synonym) is referenced in SQL code without a schema prefix, the analyser will assume that it belongs to the given default schema.

NoMY_SCHEMA

Note: if your project contains files which don't require the same default schema, you may consider using a multi-module project.

  • No labels