PL/SQL

PL/SQL analysis in SonarQube 10.4 is available starting in Developer Edition.

For AI agents: You're in the SonarQube Server 10.4 documentation. For a list of all 10.4 pages, see the SonarQube Server 10.4 page index. For the whole site, see the page index or the full text. For another version, replace 10.4 in the URL with that version. The latest version has no version number in its URL.

PL/SQL analysis is available starting in Developer Edition.

Language-specific Properties

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

Advanced parameters

Default schema

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.

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:

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.
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.

Related pages

• Adding coding rules