PL/SQL
Language-specific information about the way that SonarQube Cloud supports the analysis of PL/SQL.
Last updated
Was this helpful?
Language-specific information about the way that SonarQube Cloud supports the analysis of PL/SQL.
To discover and update the PL/SQL-specific properties, navigate in SonarQube Cloud to Your Project > Administration > General Settings > Languages > SQL. See Configuration overview for more information about setting properties.
Parameter
Description
sonar.plsql.defaultSchema
When 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.
Defaults to sonar.plsql.jdbc.user.
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:
Parameter
Description
sonar.plsql.jdbc.url
URL of the JDBC connection. Required for data dictionary lookup.
For example: jdbc:oracle:thin:@my-oracle-server:1521/my-db
sonar.plsql.jdbc.user
JDBC user to authenticate the connection.
Will be used as the default schema name if not specified otherwise via sonar.plsql.defaultSchema.
sonar.plsql.jdbc.password
JDBC password provided to authenticate the connection.
sonar.plsql.jdbc.driver.path
Path or URL of the Oracle JDBC driver JAR.
sonar.plsql.jdbc.driver.class
Java 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.
Adding the -- NOSONAR comment at the end of the line will suppress all issues on that line.
Rather than relying on this method, we suggest refining your analysis scope to avoid creating major gaps in your code review. Because the NOSONAR comment silences all current and future issues on a line without regard for their severity, it is an imprecise tool. Even if you only intend to hide a minor stylistic point, you could unintentionally obscure a serious security flaw.
The rule NoSonarCheck allows tracking in-line suppression comments in PL/SQL code.
Last updated
Was this helpful?
Was this helpful?